Add 'idle' event: fires when no further rendering is expected without further interaction. #7625
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We fairly frequently receive requests for a map event that fires when the map is "done rendering". This is a kind of squishy concept because so many things can cause the map to change. Even if there's no user interaction with the map, tiles can update at any time and trigger map updates. However, we have a pretty good idea of when we're entering an idle state:
This PR fires an
idle
event in that condition. One reason someone might want to use this event is to make changes to the map, and then do a canvas capture after everything has finished rendering.Launch Checklist
post benchmark scorestagged@mapbox/studio
and/or@mapbox/maps-design
if this PR includes style spec changescc @kkaefer @1ec5 @tmpsantos @mourner @ryanhamley @mollymerp