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

(4 留言) (0 反應) (0 負責人)JavaScript (27,768 star) (9,278 fork)batch import

P2good first issuemetrics-cwv

描述

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

貢獻者指南

技術棧: javascript
領域: performanceobservability
議題類型: research
難度: 4
預計時間: over 1 week
活動狀態: stale
清晰度: mostly clear
前置要求: Long Tasks APInavigator.scheduling.isInputPendingTBT metricTTI metric
新手友善度: 20
研究方向: 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.