Release 1.66.3
Release Notes - Seatmap Platform
Version 1.66.3 - 2026-05-21
Release Focus: Booking renderer hotfix bundle — SVG fallback escape hatch, CORS-correct background image loading, marker alignment in shared SVG mode, and marker-group preservation in setBackgroundAsOutline.
What’s Fixed
Wire SVG fallback and forceSvg escape hatch
Customers running into WebGL-specific issues (driver bugs, downsized previews on hosts that strip extensions) had no documented way to opt out and fall back to the SVG renderer for that session. The fix wires up the existing SVG fallback path and exposes a forceSvg escape hatch — both query-param and runtime config — that pins the renderer to SVG for the load. Issue: SEAT-999.
Always send Origin when loading background images
Background image requests now consistently include the Origin header so CDN/CORS responses produce the same Access-Control-Allow-Origin value across all load paths. Previously, the header was set inconsistently and certain CDN configurations responded with cached non-CORS headers, breaking image decode in the renderer.
Align markers with the WebGL stage in shared SVG mode
When the renderer was sharing an SVG background with marker overlays, the markers’ coordinate space could drift from the WebGL stage by the difference between the SVG viewBox and the WebGL clip-space — producing a small but visible offset on map markers. The fix anchors marker layout to the WebGL stage transform so both layers stay in sync at any zoom.
Preserve markers group in setBackgroundAsOutline
setBackgroundAsOutline was wiping the marker group as a side effect of replacing the underlay, requiring host apps to re-attach markers manually after every outline switch. The group is now preserved.
Affected products
booking-client— WebGL/SVG fallback path, image-loading CORS, marker alignment, outline switching.
Upgrade
npm install @seatmap.pro/renderer@1.66.3
The forceSvg opt-out is additive; existing integrations are unaffected by default.