Early-preview reference
Markdown support and preview limitations
Markover preserves the exact reviewed Markdown and maps it to review blocks according to the tested behavior below. This is a Markover product contract, not a claim of blanket CommonMark or site-specific dialect compatibility.
Behavior-level compatibility matrix
Structured blocks become navigable review-tree nodes. Opaque single blocks are selectable as a whole without child nodes. Preserved inline content stays inside its parent block rather than becoming structure. Visible uninterpreted text keeps its markers visible without extension-specific meaning. Source-only content remains in the exact reviewed source but has no review block or preview representation.
Source precision. “Exact reviewed source” means the stored document and its checksum. A review block keeps its selected content and document line range, but its compact raw text uses \n line separators even when the reviewed document uses CRLF or CR separators.
| Construct | Classification | Review and preview behavior |
|---|---|---|
| YAML frontmatter | Structured block | The complete frontmatter is one read-only container. Line-safe top-level mapping pairs become child blocks; comments, flow maps, and complex keys remain visible in the container source. |
| ATX and Setext headings; paragraphs | Structured block | Headings create the document hierarchy. Each paragraph is a selectable child of its current section. |
| Ordered and unordered lists; task markers | Structured block | Each item is selectable, and nested lists become child items. A leading [ ], [x], or [X] records task state while remaining in the item's raw block text. |
| Fenced and indented code | Structured block | Each source range becomes one code block. A fenced block's info string is retained as its language label. |
| Thematic breaks | Structured block | The complete marker line becomes one selectable block. |
| Block quotes | Opaque single block | The complete quote is selectable and rendered together. Quoted paragraphs and lists do not become child review blocks. |
| Pipe tables | Opaque single block | Markover explicitly enables pipe-table parsing. The complete table is selectable; rows and cells do not become child review blocks. |
| Emphasis, strong text, and inline code | Preserved inline content | Markers and content stay in the parent block's raw text and render inline; they do not create separate review blocks. |
| Inline links and image syntax | Preserved inline content | Labels and destinations stay in the parent block. Links remain inert. Image syntax renders as a labeled preview control; only an embedded data: source can open in the current preview. |
| Raw HTML | Visible uninterpreted text | HTML interpretation is disabled. Tags remain visible in paragraph content and do not create HTML elements or specialized blocks. |
| Strikethrough, definition-list, and footnote-call syntax | Visible uninterpreted text | Representative markers remain literal paragraph content. Markover does not create strikethrough, definition, or footnote nodes. Some standalone caret-prefixed definitions follow the source-only row below. |
| Reference-style link uses | Visible uninterpreted text | The reference use remains in its parent paragraph. Because a standalone definition is source-only and absent from the paragraph's preview input, markers such as [label][id] remain literal rather than rendering as a link. |
| Standalone reference-shaped definitions | Source-only content | A valid standalone link definition has no review block or preview representation. This includes a short caret-prefixed form such as [^note]: Note. It remains only in the exact reviewed source. |
Links stay inert; image sources stay bounded
Rendered links do not navigate when clicked in a review. Inline image syntax becomes a labeled preview control. Only an embedded data: image can open in the current preview. Relative paths, local file paths, and HTTP(S) URLs remain unavailable; choosing their controls makes no network request.
Local pasted screenshot attachments are stored with the review. Inspect attachments and review content before sharing a handoff.
The original source remains the reference
Markover retains the exact reviewed Markdown and its checksum even when a construct has no specialized tree structure or no separate block. Editing a source block creates a proposal; Markover does not rewrite the original review target.
A complete handoff therefore preserves the source for an agent or developer to inspect. The compatibility matrix describes review and preview behavior; it does not narrow the source-preservation guarantee.
Early-preview product boundary
- Markover supports macOS 14 Sonoma or newer on Apple Silicon Macs. Native Intel releases are deferred to the Broad announcement roadmap.
- The launcher requires Node.js 22.13.0 or newer.
- Current downloads are hardened and ad-hoc signed, but not Apple-verified or notarized.
- Unreleased prototype formats may change directly. Released review schemas are converted automatically with an original backup; unknown future versions remain untouched until a compatible Markover release opens them.
- Managed reviews and their unused attachments can be moved to the macOS Trash from Markover. Cache management and a complete reset use the procedures in Privacy, storage, and recovery.
Ask about a document or report a defect
Use GitHub Discussions when you are unsure whether a document or syntax will work well. Use the bug report form for a reproducible defect, including the smallest sanitized example that demonstrates it.