Contact emailsnrosent...@chromium.org Specificationhttps://w3c.github.io/longtasks
Summary Using the LoAF implementation for reporting longtasks is an implementation detail, but it would have the following web-observable impact: - we would stop reporting longtasks for hidden tabs - a few longtask bugs would disappear, resulting in more reported longtasks Note that this would not affect the Lighthouse TBT score, that anyway relies on trace events. Blink componentBlink>PerformanceAPIs <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPerformanceAPIs> TAG reviewNone TAG review statusNot applicable Risks Interoperability and Compatibility This doesn't change the spec, and mostly improves maturity and maintainability. The main compat risk is with the behavior change that longtasks in hidden tabs are not reported, however that's anyway a brittle concept as background documents often undergo all kinds of throttling, making their reported longtasks not actionable. *Gecko*: N/A *WebKit*: N/A *Web developers*: No signals *Other signals*: WebView application risks Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications? None Debuggability None Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?Yes Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ?Yes Existing tests: https://wpt.fyi/results/longtask-timing?label=experimental&label=master&aligned This would fix some of them. Flag name on chrome://flagsLongTaskFromLongAnimationFrame Finch feature nameLongTaskFromLongAnimationFrame Requires code in //chrome?False Tracking bughttps://issues.chromium.org/issues/40266553 Estimated milestones Shipping on desktop 124 Shipping on Android 124 Shipping on WebView 124 Anticipated spec changes 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 Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5146440839200768 This intent message was generated by Chrome Platform Status <https://chromestatus.com/>. -- 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+unsubscr...@chromium.org. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYYtPfYwA6mCFECnRS2f--kzmfUs6%3DZwP-tEkwou53sOLw%40mail.gmail.com.
