Intent to Extend Experiment: SoftNavigation performance Entry

[Yoav Weiss]

Contact emails

yoav...@chromium.org

Explainer

https://github.com/WICG/soft-navigations#soft-navigations

Specification

https://wicg.github.io/soft-navigations

The spec is still pretty initial and rough, but should give a general idea of how this can integrate with the platform.

Summary

Exposes the (experimental) soft navigation heuristics to web developers, using both PerformanceObserver and the performance timeline.

Blink component

Blink>PerformanceAPIs

TAG review

https://github.com/w3ctag/design-reviews/issues/879

TAG review status

Extremely recent.

Risks

Interoperability and Compatibility

Gecko: No signal on an extremely recent position request https://github.com/mozilla/standards-positions/issues/854

WebKit: No signal on an extremely recent position request

https://github.com/WebKit/standards-positions/issues/235

Web developers: Strong support!

Interesting results from OT participants.

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?

Nope!

Goals for experimentation

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.

Reason this experiment is being extended

Not enough feedback the first time around. But partners tell me they are now ready to measure using this.

Ongoing technical constraints

None.

Debuggability

Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?

Yes

Is this feature fully tested by web-platform-tests?

Yes!

Flag name

SoftNavigationHeuristics

Requires code in //chrome?

False

Tracking bug

https://bugs.chromium.org/p/chromium/issues/detail?id=1338390

Estimated milestones

Origin Trial ran from M110-M114 (ending on June 30th). I asked to extend it on that thread, but never did.

I'm interested in running a trial on M117-M120 (inclusive), skipping most of M115 and M116 to ensure lack of reliance on the OT.

Link to entry on the Chrome Platform Status

https://chromestatus.com/feature/5144837209194496

Links to previous Intent discussions

Intent to prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfV3qRFx0i-eGJFSzqE8bnbX8XYJCvXAj0LfvO0icPo_jA%40mail.gmail.com

Intent to experiment: https://groups.google.com/a/chromium.org/g/blink-dev/c/IK-IZTBo59U/m/r8WaR2YOBQAJ

[Mike Taylor]

LGTM to extend from M117-M120 inclusive, especially with the pause in 115 and 116. 

Thanks for demonstrating spec progress and sharing OT results (I'm not going to pretend I watched that whole 42 minute video tho - I trust that you did. ^__^).

--
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/CAL5BFfULP5d3fNCAqeO2gLP56R3HCytmaNk%2B9kpYsC2dj4%3DqoQ%40mail.gmail.com.