DocsBrowser-only alpha
Production checklist
What to verify before using the beta in a customer-facing workflow.
Use this checklist before a pilot or customer-facing export flow.
Document layout
- Printable root has an explicit width.
- Width fits the target page content area.
- A4 +
20mmmargins starts around640pxDOM width. - Long rows/cards that should stay together use
break-inside: avoid. - Manual chapter/report breaks use
<PageBreak />orbreak-before: page.
Fonts
- Every production font is available as TTF or OTF.
- Every used weight/style is registered before export.
- DOM CSS
font-familymatches the registered family name. - Fallback PDF output has been checked by intentionally disabling a font URL once.
Images
- Images are PNG or JPEG.
- Remote images pass CORS.
- Logo/images repeated across pages use the same
srcso deduplication works. - Any
object-fitdependency has been visually checked or avoided.
Raster fallback
- Complex visual widgets are intentionally marked with
data-pdf-raster="true". - Large raster regions are avoided.
- Raster text is acceptable for those regions.
- Cross-origin fonts/images inside raster regions are self-hosted or CORS-enabled.
Pagination
- Headers and footers fit inside the configured margins.
- Multi-page tables use
data-print-repeaton<thead>or an equivalent header band. - Generated PDFs have been checked at 100%, 200%, and text-selection view.
- Page count and page-number labels have been verified on the longest known document.
Delivery
- Use
result.save()for direct download. - Use
result.blob()for upload or preview in your own UI. - Use
result.bytes()for tests and low-level integrations. - Do not keep object URLs forever; the built-in
save()andpreview()helpers revoke their temporary URLs.
Browser support
Run the same export fixture in:
- Chromium
- Firefox
- WebKit/Safari
The repo already uses Playwright across browser engines. Add your own customer document fixtures once the export becomes part of a critical workflow.