Skip to content

Fix font-family cascade in the packaged engine - #66

Merged
krflol merged 1 commit into
mainfrom
fix/engine-2-5-29
Nov 1, 2026
Merged

krflol merged 1 commit into
mainfrom
fix/engine-2-5-29

Conversation

@krflol

@krflol krflol commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

Fullbleed 0.9.4 for JavaScript embeds engine 2.5.51. Concrete font-family declarations now replace losing custom-property values correctly. An invalid winning custom-property value inherits the parent font. The JavaScript API is unchanged.

npm install fullbleed@0.9.4

All 13 CI jobs passed: nine installed-package combinations across Windows, Linux and macOS with Node 22, 24 and 26; Chromium, Firefox and WebKit; and the native/WASI output checks. Existing component, queue, batch, pagination, paint, counter and font gates remain in place.

Thirteen saved font witnesses pass independently in Linux and Windows, with matching PDF and PNG bytes. The actual public 0.9.3 package reproduces eleven incorrect font selections and two healthy controls; 0.9.4 corrects the eleven and preserves both controls. A fresh installation of the exact release tarball also passes all thirteen witnesses, and all 50 installed payload files match the archive. The evidence archive includes retained output and its checks.

These are fixture-specific results, not a claim of complete browser CSS support. The expanded component API remains alpha.

Change review. Verified source: 5dd773f972f5b3a4231b17496eb61e96b20b001e.

@krflol
krflol marked this pull request as ready for review November 1, 2026 18:48
@krflol
krflol merged commit 93e5583 into main Nov 1, 2026
13 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant