Add explainer for the Congested Moment API#1298
Open
joone wants to merge 1 commit intoMicrosoftEdge:mainfrom
Open
Add explainer for the Congested Moment API#1298joone wants to merge 1 commit intoMicrosoftEdge:mainfrom
joone wants to merge 1 commit intoMicrosoftEdge:mainfrom
Conversation
joone
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The Delayed Message Timing API is the predecessor proposal that introduced per-message timing attribution. The Congested Moment API builds on its concepts, elevating them to an interval-level view of execution context congestion. Per-message timing attribution has a problem with duplicate script entries because the same scripts can block multiple adjacent messages. Instead, the focus shifts to the congested moment caused by those scripts, attributing the impacted messages to it. This shift also brings a broader perspective: rather than viewing congestion message-by-message, the Congested Moment API reasons at the execution context level. This makes it possible to attribute not only delayed messages but also other affected UI events to the same source of congestion.