Skip to content

fix(tile_layer): Keep loaded descendants when an ancestor is also available - #2267

Open
nebkat wants to merge 1 commit into
fleaflet:masterfrom
nebkat:fix/retain-descendants-while-zooming-out
Open

nebkat wants to merge 1 commit into
fleaflet:masterfrom
nebkat:fix/retain-descendants-while-zooming-out

Conversation

@nebkat

@nebkat nebkat commented Sep 17, 2026

Copy link
Copy Markdown

staleTiles and renderTiles only looked for descendants if the ancestor walk came up empty. _retainAncestor stops at the first loaded tile up to five levels above, and neighbouring tiles share ancestors, so one cached tile was enough to drop the descendants across the whole view. Zooming out shows it: the sharp tiles already on screen are discarded for a coarse cached ancestor before the new level loads.

They are not alternatives, so keep both until the target level is ready. renderOrder already draws the higher resolution ones on top where they overlap.

…ilable

staleTiles and renderTiles only looked for descendants if the ancestor walk came
up empty. _retainAncestor stops at the first loaded tile up to five levels above,
and neighbouring tiles share ancestors, so one cached tile was enough to drop the
descendants across the whole view. Zooming out shows it: the sharp tiles already
on screen are discarded for a coarse cached ancestor before the new level loads.

They are not alternatives, so keep both until the target level is ready.
renderOrder already draws the higher resolution ones on top where they overlap.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant