Repository navigation
Try the released PDF engine directly in the browser - #7
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.
Visitors can now edit HTML/CSS and generate Fullbleed PDFs directly on the documentation site, without an account or a local install. The playground opens with the designed invoice and also includes the illustrated three-page report and service notice, with embedded fonts, page navigation, source downloads, and PDF downloads.
An optional Rust adapter pins the published fullbleed 2.5.0 crate and compiles it to WASI. A worker runs it against an in-memory filesystem using the pinned browser_wasi_shim 0.4.2 package. User source is never added to the page DOM or submitted to a server. No core-engine or Python-package change is needed. Builds retain dependency/font licenses, source hashes, and verification records.
The demo enforces a six-page/200 KB source limit, 256 MiB WASM memory ceiling, a render timeout, cancellation, and clean recovery after errors. These limits are specific to the website demo.
Validation:
The documentation CI now rebuilds and verifies the native and WASI adapter before deploying, and uploads its evidence. These checks cover the included fixtures, not universal browser parity or PDF conformance certification.