Exposes the (experimental) soft navigation heuristics to web developers, using both PerformanceObserver and the performance timeline.
Does this intent deprecate or change behavior of existing APIs, such that it has potentially high risk for Android WebView-based applications?
I'm interested in gaining insights on the quality of the heuristic and how it compares to current heuristics employed by RUM providers or driven by framework- or app-specific knowledge. I'm also interested in knowing if developers find the correlation of various performance entries to their soft navigation ergonomic, and whether the emitted FP/FCP/LCP entries work well for them to evaluate the performance of their soft navigations.
|OriginTrial desktop last||112|
|OriginTrial desktop first||109|
|OriginTrial Android last||112|
|OriginTrial Android first||109|
|OriginTrial webView last||112|
|OriginTrial webView first||109|
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/CAL5BFfUb_Gn_5gGy8SnChg5KH2JN57Gv0NhnHN7Q_kH0Aa17CQ%40mail.gmail.com.