Skip to content

Fullbleed 0.3.1: styled inline wrapping and label sizing

Choose a tag to compare

@krflol krflol released this 06 Oct 12:19

Fullbleed 0.3.1 fixes text overlapping its prefix when paragraphs wrap around styled spans or code. It also keeps tracked flex and inline-block labels at their intended width. The Node and browser entries use the published Fullbleed 2.5.10 engine.

npm install --save-exact fullbleed@0.3.1

The API and runtime dependencies are unchanged. Affected line breaks, pagination, and PDF hashes can change; review saved baselines when upgrading.

The release tarball passes all 13 CI jobs: a native-engine comparison, Node 22/24/26 on Linux/macOS/Windows, and Chrome/Firefox/Playwright WebKit. Each browser passes 66 checks, including actual PDF/PNG downloads, worker cancellation and recovery, and same-origin asset requests without document uploads. WebKit testing is not branded Safari testing.

The 24 installed-package inline cases cover both Node isolation modes. Public 0.3.0 fails twenty styled cases while its four plain controls pass. All 19 native/Wasm PDFs match; exact preview equality is required for the 17 fixtures that use embedded fonts. Explicit unembedded Helvetica/Times native previews can use host fonts absent from Wasm, so use bundled or registered fonts for Fullbleed previews.

The font gate retains the original outlines, glyph IDs, metrics, mappings, and notices. Five font-only layouts remain identical to the retained 0.1.3 baseline. The invoice and report match exact reviewed PDF and preview hashes with single-line footers; their reports explicitly identify the layout changes. No general visual-parity or PDF standards-conformance claim is made.

The separate native runtime investigation #7 remains open; this release does not establish a fix for that intermittent crash.

See PR #22, the inline checks, and the font verification. Attached artifacts retain the tarball, source provenance, inputs, PDFs, previews, and checksums.