Repository navigation
Fullbleed 0.9.1: fonts in page headers and footers
Fullbleed Node 0.9.1 fixes custom font aliases in page headers and footers by bundling engine 2.5.48. A family declared through @font-face, such as Brand, now selects the registered font in page-margin text as well as document content.
npm install --save-exact fullbleed@0.9.1Use the alias in @page or a margin box. To inherit a document-wide page font, set the family on html; a font set only on body does not set the page font. Use defaultStyles: false when your stylesheet should control document inheritance. The fix covers escaped names, fallback families, descriptor selection, size-adjust, and first/named pages. See the font and asset reference.
All 13 source-CI jobs passed: installed packages on Node 22, 24 and 26 across Linux, macOS and Windows, and browser checks in Chrome, Firefox and WebKit. The new page-font check compares eight alias/control pairs (16 documents, 18 pages) on Windows and Linux with the qualified native engine outputs. PDF bytes, native previews and independent PDFium output match; the saved PDFs also pass text, embedded-font, footer-size and glyph-bound checks. A fresh installation of the exact CI tarball reproduces the result. Public 0.9.0 is retained as the negative control.
The intentionally broken 0.9.0 control has seven pages with unembedded Helvetica whose PDFium substitute pixels differ between Windows and Linux; its structural failure checks agree. The candidate font pages match exactly.
The existing compiled-batch, component, HTML-export, Workers, paint and pagination release checks remain required. The standalone Workers starter now pins this package version. Component authoring remains alpha. These fixtures do not establish complete CSS or PDF conformance, hosted Workers suitability, performance, or independent adoption.
- Verification record and retained inputs, PDFs, previews and checks.
- Reviewed source:
39e162b19e460bf3541fbbbad775b4bfa7929a23; exact-source CI.