handling impact of isInputPending on long tasks metrics? · GoogleChrome/lighthouse#11747

(4 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)JavaScript (27.768 Stars) (9.278 Forks)batch import

P2good first issuemetrics-cwv

Beschreibung

navigator.scheduling.isInputPending is shipping by default in current Chrome stable (m87). Without user input, any page using isInputPending has a strong reason to believe yielding during long tasks won't improve user experience so it could keep on chugging instead.

This may have a large impact on any metric looking at long tasks (TBT, TTI) compared to what a real user would experience when loading the same page.

There was a discussion in the WICG about how it should interact with the Long Tasks API and warnings against long tasks, as well if there should be a way to tell if isInputPending was called during a particular long task: https://github.com/WICG/is-input-pending/issues/37
Chrome status entry

Contributor Guide

Tech Stack: javascript
Domain: performanceobservability
Issue Type: research
Schwierigkeit: 4
Geschätzte Zeit: over 1 week
Aktivitätsstatus: stale
Klarheit: mostly clear
Voraussetzungen: Long Tasks APInavigator.scheduling.isInputPendingTBT metricTTI metric
Einsteigerfreundlichkeit: 20
Research-Richtung: Investigate the WICG discussion at https://github.com/WICG/is input pending/issues/37 to understand proposed interactions with Long Tasks API. Review Chrome status entry for implementation details. Assess impact on Lighthouse's TBT and TTI audits by considering how isInputPending affects long task duration. Propose whether to incorporate isInputPending detection into existing metrics or add a new audit.