Testing & Browser Support

The package targets modern browsers supported by Vue and the underlying PDF/browser APIs.

Recommended testing:

• Chromium / Chrome / Edge
• Firefox
• WebKit
• Safari when Safari is important to production users

Playwright WebKit tests the WebKit engine; it is not identical to testing the Safari application itself.

Testing

The Phase 4 source includes unit tests for smart splitting, table continuation, slots, composition, page geometry and cancellation. A historical package run recorded 235 tests across 43 files; a later performance/slot record reported 357 tests across 45 files and successful library/playground builds. Those runs preceded or accompanied subsequent fixes and are not a fresh full acceptance pass. The earlier Chromium Phase 4 browser run passed 5 of 6 tests, with an A4 portrait preview-iframe timeout that passed in isolation. The latest browser visual, full E2E and stress reruns were deferred. Firefox/WebKit Phase 4 acceptance was not part of that audit. Inspect representative PDFs, especially continued tables, nested frames, slots and format/orientation combinations.

The v1 testing guide preserves the previous release's test narrative. A docs build does not run package browser suites.

Media and typography verification for v1.3.0

The media verification record includes a 380-test unit run, TypeScript checks, library and playground builds, focused Chromium/WebKit browser exports, and selected rendered-page visual checks. A later named format/orientation matrix passed 82 combinations. Follow-up pagination and footer changes have their own narrower checks, including an inspected nine-page selectable-text report; those checks do not make every earlier suite current. Local Firefox verification remains open because its headless graphics compositor failed at launch. The docs-site build below checks documentation output only. See media and typography for the tested feature boundaries.

The release verification covers major public workflows, including:

• Canvas and selectable-text PDF generation
• Blob, ArrayBuffer and Base64 output APIs
• preview Blob creation
• download
• native browser print flow
• rendering mode routing
• selectable-text generation
• PDF link annotations
• pagination and page-break mapping
• data-pdf-ignore
• export-only page/body styling
• themes, custom CSS, external stylesheets and auto-fit
• metadata
• compression
• security
• protected/unprotected PDFs
• header page targeting
• selective header spacing
• optional header/footer logos
• custom logo sizing
• header/footer HTML rendering
• selectable header/footer text
• footer page numbering
• per-page watermark targeting
• progress stages
• page-aware currentPage / totalPages
• opt-in generation metrics
• cooperative cancellation and recovery
• portrait and landscape layouts
• large-document regression/stress scenarios
• selectable repeated-image caching
• page-bounded Canvas image-heavy rendering
• temporary rendering DOM/snapshot cleanup
• SSR-safe package import
• Nuxt 3 and Nuxt 4 SSR/hydration/client navigation

Package-manager consumer matrix

Packed-package consumer fixtures run against:

• npm
• pnpm
• Yarn
• Yarn Plug'n'Play
• Bun

These fixtures verify install behavior, TypeScript resolution, production builds, CSS imports, and runtime PDF generation.

Because PDF rendering is CPU-heavy, a small Playwright worker count is recommended:

npx playwright test --workers=2

Use a single worker for heavy stress/regression suites:

npx playwright test --workers=1

Run the package's release checks before publishing changes to the PDF library itself. Application consumers should also test representative real documents on the browsers and devices that matter to their users.