Browser compatibility

The cross-browser contract for Chrome, Edge, Firefox, and Safari, including the checks required before release.

One Web Component across major engines

DocViewKit targets current Chrome and Edge Chromium, Firefox Gecko, and Safari WebKit with the same Web Component API. The host supplies a File, Blob, ArrayBuffer, or Uint8Array; the Viewer owns parsing, rendering, search, navigation, and diagnostics.

Compatibility means the documented API and bounded viewing workflow remain available across the supported engines. It does not mean every browser uses identical font shaping, media codecs, color management, canvas limits, or print behavior.

Release checks

  • Open a real document through the public Viewer entry point.
  • Verify navigation, search, zoom, close and reopen, diagnostics, and source location.
  • Run the same interaction contract in Chromium, Firefox, and WebKit.
  • Treat a browser-specific omission or degraded path as a release failure or a published diagnostic boundary.