Portable browser
Common standards-based document flow: print media, page size/margins, native fragmentation, multicolumn layout, semantic tables, and graceful fallback.
Folio does not pretend every browser or PDF engine implements the same paged-media surface. The component API expresses document intent; capability tiers describe what the selected renderer can actually guarantee.
Common standards-based document flow: print media, page size/margins, native fragmentation, multicolumn layout, semantic tables, and graceful fallback.
Controlled Chromium support for authored page-margin headers/footers and physical Page X of Y counters.
Pinned automation, font/image readiness, background policy, browser chrome disabled, and recorded renderer diagnostics.
Optional publishing engines for richer running content, target counters, footnotes, sidenotes, bleed, marks, and related advanced features.
| Capability | Current posture | Evidence |
|---|---|---|
| Passive light-DOM print wrappers | Accepted | PAGINATION-01 showed no geometry difference from native wrappers across tested engines. |
| Native multicolumn flow | Accepted | COL-01 passed representative multipage fragmentation. |
| Grid side rail | Provisional | SIDEBAR-01 preserved markers/separation in Chromium; deeper descendant/cross-browser proof remains open. |
| Chromium page-margin boxes | P1/P2 only | MARGIN-01 validated static running content and Page X of Y in controlled Chromium. |
| Header/footer/page-number primitives | Core intent shipped; repetition/counters capability-bound | Cross-browser primitive contract validates in-flow fallback; MARGIN-01 remains the physical counter evidence. |
| Artwork layer | Accepted element-layer pattern | ART-01 validates that essential foreground content survives when page artwork is suppressed. |
| Table primitive | Accepted wrapper contract | TABLE-01 validates long-table header repetition, row behavior, and named landscape output in controlled Chromium. |
| Callout, figure, code, TOC, note | P0 core shipped | Cross-browser primitive contract plus generated mobile examples validate passive light-DOM/CSS behavior; enhanced placement remains capability-bound. |
| Publication recipes (journals, proceedings, books) | P0 recipes; running heads P1/P2 | JOURNAL-ARTICLE-01 and JOURNAL-ISSUE-01 validate fragmentation, spans, landscape pages, and continuous counters in controlled Chromium; recipe contracts run in Chromium, Firefox, and WebKit. |
| Running strings, first-page suppression in named-page groups, target-page references, footnotes, recto starts | P3 experiment only | Chromium 141 does not implement them (EV-PRINT-2026-0007); JOURNAL-ENHANCED-01 compares an optional engine (EV-PRINT-2026-0008). |
| Tagged/PDF-UA quality | Separate validation track | Semantic HTML is necessary but browser PDF tagging is not assumed. |
A document containing a Folio component is not evidence that every renderer can honor every requested physical-page feature. Consumers that require a feature must select or validate a renderer profile that provides it.