Frontend runtime compatibility

One Web Component across major engines

The Viewer runs in frontend environments that provide DOM/Custom Elements, module Workers, WebAssembly, Canvas/OffscreenCanvas, ImageBitmap, and FontFace. These include browsers and compatible WebView hosts in Electron, Tauri, Ionic and Capacitor. React Native and Flutter applications can embed it through a WebView that provides the same APIs; their native rendering layers do not run the Web Component directly. Validate the actual host engine, asset loading, CSP, fonts, and required interactions on each target platform. Browser hosts include Chrome, Edge, Firefox and Safari. 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.