Description
When the Google Maps container (or an ancestor element) is styled using CSS transform (e.g., transform: scale()), the GoogleMapsOverlay` canvas fails to calculate its dimensions and absolute DOM position correctly. As a result, the deck.gl canvas does not fully align with or cover the Google Map instance, leading to misaligned layers and unrendered/clipped data points.
Flavors
GoogleMapsOverlay
Expected Behavior
- The canvas element of deck.gl should fully cover Google Maps (both raster and vector types).
- Layers can be correctly rendered with no missing parts.
Steps to Reproduce
- Disable GPU acceleration in Chrome settings so that Google Maps falls back to raster type.
- Open https://developers.google.com/maps/documentation/javascript/examples/deckgl-tripslayer
- Open DevTools and modify
<body> with transform: scale(0.5).
- See the deck.gl canvas size and positioning are not aligned with Google Maps. Trip lines are no longer visible on some parts.
Environment
- Framework version: deck.gl 9.2.11 ~ 9.3.6
- Browser: Chrome 152, Edge 152
- OS: Windows, MacOS
Logs
No response
Description
When the Google Maps container (or an ancestor element) is styled using CSS
transform(e.g.,transform:scale()), theGoogleMapsOverlay` canvas fails to calculate its dimensions and absolute DOM position correctly. As a result, the deck.gl canvas does not fully align with or cover the Google Map instance, leading to misaligned layers and unrendered/clipped data points.Flavors
GoogleMapsOverlay
Expected Behavior
Steps to Reproduce
<body>withtransform: scale(0.5).Environment
Logs
No response