Record task-like timing in fire an event#1462
Open
noamr wants to merge 4 commits into
Open
Conversation
Together with w3c/long-animation-frames#37 This allows clustering a "fire an event" timeframe in terms of frame timing monitoring, as opposed to relying on an "implicit document", which is a deprecated and non-interoperable term. The implication of this is that if this event firing schedules a render that ends up as a long animation frame, the whole event firing duration would be counted towards this performance entry, regardless of "tasks". See w3c/long-animation-frames#36
Co-authored-by: Anne van Kesteren <annevk@annevk.nl>
Contributor
Author
|
@smaug---- can I enlist mozilla as interested in this? This is done after our conversation to enable some bits of long animation frames for gecko. |
annevk
approved these changes
May 22, 2026
Member
annevk
left a comment
annevk
left a comment
There was a problem hiding this comment.
Looks good modulo nit. Can land once OP is done.
|
|
||
| <ol> | ||
| <li><p>Let <var>recordingTimingAsTask</var> be the result of calling <a>start recording task time if | ||
| needed</a> given <var>target</var>'s <a>relevant settings object</a>. |
Member
There was a problem hiding this comment.
Oh also this contains a newline inside phrasing
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
3 participants
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.
This allows clustering a "fire an event" timeframe in terms of frame timing monitoring, as opposed to relying on an "implicit document", which is a deprecated and non-interoperable term.
The implication of this is that if this event firing schedules a render that ends up as a long animation frame, the whole event firing duration would be counted towards this performance entry, regardless of "tasks".
This is already how long animation frames behave in the chromium implementation and should be unobservable from the previous spec wording that relied on "implicit document".
See w3c/long-animation-frames#36
(See WHATWG Working Mode: Changes for more details.)
Preview | Diff