Repository navigation
Fix blank font previews in public JavaScript starters - #71
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Pasted HTML/CSS using standard PDF fonts produces blank previews in the old public demos. Refresh the browser, React, Vue, and Next.js ZIPs to published Fullbleed 0.3.2 / engine 2.5.11 from the verified source in fullbleed-engine/fullbleed-node#27. The hosted demos and online launchers are built from those exact ZIPs.
Carry the edited-template preview regression check into documentation CI, update version/provenance text, and regenerate the Next.js verification record from its three platform runs. Designed invoice/report PDF and preview hashes remain unchanged.
Validation: source CI passed across Chrome/Firefox/WebKit, React StrictMode, and three Next.js platform combinations. All four exact ZIPs pass local builds and output checks; each anonymous StackBlitz project starts, supports real source editing, downloads its PDFs, and renders standard-font previews. Eight desktop/mobile guide-and-ZIP checks, strict MkDocs build, and 73-page link/metadata checks pass. The old live 0.3.1 demos were retained as blank-preview controls; no new SDK release or broad conformance claim.