You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Symbols with *-allow-overlap: true default to being visible before placement happens, so we can show them immediately when their tile loads. However, if they are included in a placement while they are far enough outside the viewport, CollisionIndex::placeFeature won't place them. This is a performance optimization: we don't want to clutter the CollisionIndex with lots of stuff that's far off screen. The problem is that when this happens, we override the default "visible" state for the symbols, and when the map is panned to bring them on-screen, they won't become visible until the next placement happens (and when it does, they'll have to fade-in).
When we implement this in GL JS, we should also implement a render test that uses a non-zero fadeDuration, loads a symbol outside of the grid range, then pans over before placement/fade has had a chance to run and verifies the symbol is already visible.
GL JS version of mapbox/mapbox-gl-native#12683, port of mapbox/mapbox-gl-native#12698.
When we implement this in GL JS, we should also implement a render test that uses a non-zero
fadeDuration
, loads a symbol outside of the grid range, then pans over before placement/fade has had a chance to run and verifies the symbol is already visible.cc @ansis @ryanhamley
The text was updated successfully, but these errors were encountered: