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.
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.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
None
None
Existing tests: https://wpt.fyi/results/longtask-timing?label=experimental&label=master&aligned This would fix some of them.
Shipping on desktop | 124 |
Shipping on Android | 124 |
Shipping on WebView | 124 |
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