This is a 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). However, this is anyway observable, by using requestAnimationFrame. 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?
None
OriginTrial desktop last | 120 |
OriginTrial desktop first | 115 |
OriginTrial Android last | 120 |
OriginTrial Android first | 115 |
OriginTrial webView last | 120 |
OriginTrial webView first | 115 |
--
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%3DMYbdL3atq6FvsfrR%3DVs%2Boexvt04zfjV97BNNPL76iPTGLg%40mail.gmail.com.