Release Notes - Seatmap Platform
Version 1.59.3 - 2026-02-26
Release Focus: Safari Compatibility Fix - Background Image Loading
What’s New
This is a hotfix release addressing a critical rendering issue on Safari (macOS) where the seatmap background would fail to load, causing the venue map to disappear.
Bug Fixes
Critical Fixes
- Background image fails to load on Safari (414 Request URI Too Long): When the blurred background preview is delivered as inline base64 data, the renderer incorrectly treated it as a relative URL path. This caused the browser to construct an enormous HTTP request (appending the entire base64 payload to the page URL), which the server rejected with a 414 status code. The seatmap would then render without any background image.
- Affected browsers: Safari on macOS (stricter URL length limits than Chrome/Firefox)
- The renderer now correctly detects inline base64 PNG data and wraps it as a proper data URL
- Improved error messages for image loading failures to include the target URL for easier debugging
What’s Inside
This release includes a targeted fix for background image loading:
Main Changes:
- Base64 detection in URL resolver - Raw base64 PNG data is now recognized and wrapped as a
data:image/png;base64,...URL before loading - Image load error reporting - Error handler now includes a truncated URL preview and handles browser-specific error object differences
Components Updated:
- Booking Client (Renderer) - Background image URL resolution and error handling
Migration Guide
For Existing Users
Excellent News: This release is 100% backwards compatible.
No code changes required No configuration updates needed No database migrations required Drop-in replacement for previous version
Testing Recommendations
- Safari testing: Load a venue with a blurred background preview on Safari (macOS) and confirm the background renders correctly
- Cross-browser: Verify background loading still works on Chrome and Firefox
- Existing venues: Confirm previously created venues load without any changes
Questions? Contact the Seatmap team or check our documentation at seatmap.pro.