This is an extension of long tasks. It measures the task together with its subsequent rendering update, adding information such as long running scripts, rendering time, and time spent in forced layout and style ("layout thrashing"). Developers can use this as a diagnostic for "sluggishness", which is measured by INP, by finding the causes for main-thread congestion which is often the cause for bad INP.
It should work well with other performance timeline entries, mainly event-timing/INP.
This feature exposes rendering time to iframes, which might be cross-origin (same-process). This is already observable today, by using requestAnimationFrame. Underwent internal security review. Note that everything in this feature is same-process.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
N/A
https://wpt.fyi/results/long-animation-frame/tentative?label=experimental&label=master&aligned
Shipping on desktop | 123 |
OriginTrial desktop last | 123 |
OriginTrial desktop first | 116 |
Shipping on Android | 123 |
OriginTrial Android last | 123 |
OriginTrial Android first | 116 |
Shipping on WebView | 123 |
OriginTrial webView last | 123 |
OriginTrial webView first | 116 |
Shipping on WebView | 123 |
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
None. The issues raised in the TAG reviewed were previously addressed in the security review of this feature, and need some clarification but not spec changes.Contact emails
nrose...@chromium.orgExplainer
https://github.com/w3c/longtasks/blob/loaf-explainer/loaf-explainer.md
Summary
This is an extension of long tasks. It measures the task together with its subsequent rendering update, adding information such as long running scripts, rendering time, and time spent in forced layout and style ("layout thrashing"). Developers can use this as a diagnostic for "sluggishness", which is measured by INP, by finding the causes for main-thread congestion which is often the cause for bad INP.
Blink component
Blink>PerformanceAPIsTAG review
https://github.com/w3ctag/design-reviews/issues/911
TAG review status
Issues addressedChromium Trial Name
LongAnimationFrameTimingLink to origin trial feedback summary
https://github.com/w3c/longtasksOrigin Trial documentation link
https://github.com/w3c/longtasks/blob/main/loaf-explainer.mdRisks
Interoperability and Compatibility
Gecko: Positive Not yet a formal signal but showed positive interest at WG call.
WebKit: No signal
Links to previous Intent discussions
Intent to prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYbX%3DEOAwkEvDQY9Ja1trSXLFtM1XNsuw1Lr2QR88%2BTnqw%40mail.gmail.com Intent to Experiment: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYbdL3atq6FvsfrR%3DVs%2Boexvt04zfjV97BNNPL76iPTGLg%40mail.gmail.com
Intent to Extend Experiment: https://groups.google.com/a/chromium.org/g/blink-dev/c/MClbXXUhOTs
Intent to Ship: https://groups.google.com/a/chromium.org/g/blink-dev/c/MClbXXUhOTsThis intent message was generated by Chrome Platform Status.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYZ9AtHwBuXzz%3D7B7wZyrGqbhv5F%2BYVxDm8Lc6TV2LEkDg%40mail.gmail.com.
Thanks for working on this important problem! :)
On Fri, Jan 12, 2024 at 11:31 AM Noam Rosenthal <nrose...@chromium.org> wrote:Contact emails
nrose...@chromium.orgExplainer
https://github.com/w3c/longtasks/blob/loaf-explainer/loaf-explainer.mdCan the explainer be updated? e.g. I'm assuming that the "this is a work in progress... lots of things might change" disclaimer is no longer valid.
Beyond that, the script attribution parts are not really explained outside of examples. Is there some developer-facing documentation covering that elsewhere?For example, it'd be good to cover how code is attributed for async calls, Promises that got resolved, etc.
The link above is broken. I think you meant https://w3c.github.io/longtasks/#sec-PerformanceLongTaskTiming
Regarding the spec, I see that it's monkeypatching WebIDL, DOM and HTML. This feels odd in a WG-adopted spec.Have you tried to PR these changes upstream?
Summary
This is an extension of long tasks. It measures the task together with its subsequent rendering update, adding information such as long running scripts, rendering time, and time spent in forced layout and style ("layout thrashing"). Developers can use this as a diagnostic for "sluggishness", which is measured by INP, by finding the causes for main-thread congestion which is often the cause for bad INP.
Blink component
Blink>PerformanceAPIsTAG review
https://github.com/w3ctag/design-reviews/issues/911The discussion seems to still be ongoing..
TAG review status
Issues addressed
Chromium Trial Name
LongAnimationFrameTimingLink to origin trial feedback summary
https://github.com/w3c/longtasksOrigin Trial documentation link
https://github.com/w3c/longtasks/blob/main/loaf-explainer.mdRisks
Interoperability and Compatibility
Gecko: Positive Not yet a formal signal but showed positive interest at WG call.
WebKit: No signalCan you link to the position requests?
Web developers: Positive (https://twitter.com/jebbacca/status/1653355406368952321) Wix, Microsoft, RUMVision and others have already experimented with this in Canary. Strong excitement from several partners at We Love Speed conference.
Regarding the spec, I see that it's monkeypatching WebIDL, DOM and HTML. This feels odd in a WG-adopted spec.Have you tried to PR these changes upstream?
LGTM1
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/1fe0c37e-d02c-474e-824f-498d7866c598n%40chromium.org.
I found some interesting test failures at https://wpt.fyi/results/long-animation-frame/tentative/loaf-source-location-redirect.html?label=experimental&label=master&aligned . Do they represent anything worth worrying about, e.g. a potential breaking change? Assuming not, LGTM2.
--
You received this message because you are subscribed to the Google Groups "blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to blink-dev+...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/000000000000e18baf060fb03dd3%40google.com.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYZU6mo7A42gsmBa97UUn3CJG_iuQR9HueVyUOmgdiXMqQ%40mail.gmail.com.