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
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Browsers leave microticks in-between propagating an event up, this can be seen in research performed here. Our first attempt at fixing this was using setTimeout which caused other issues to occur. This fix is a bit different rather than changing our scheduling we place a timestamp on the event-handler so we can check whether the event is appropriate to fire.
This bug can occur when we switch in a dom-node i.e. when we go from
<div><divonClickto<divonClick><div
when the inner div changes the dom-structure then we would perform the patch before the event could bubble up.
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.
Browsers leave microticks in-between propagating an event up, this can be seen in research performed here. Our first attempt at fixing this was using
setTimeout
which caused other issues to occur. This fix is a bit different rather than changing our scheduling we place a timestamp on the event-handler so we can check whether the event is appropriate to fire.This bug can occur when we switch in a dom-node i.e. when we go from
when the inner div changes the dom-structure then we would perform the patch before the event could bubble up.
fixes #3927
You can see this approach working in the following sandbox - due to this being related to browser timings I could not create a test