LGTM to keep going until M115.

On 6/14/23 3:13 AM, Yoav Weiss wrote:
I recently discovered that despite me asking for this to run till M113, the OT is running till M115. The reason I haven't "renewed" the OT after M113 is that lined-up partners took a particularly long time to add support, which resulted in practically no-use for the OTed API (beyond a very small number of origins <https://docs.google.com/spreadsheets/d/1ZC-lHLLQrAmSyfiO21EbM6LAEUjeF4x8O0J-YdYeQrI/edit?usp=sharing> - Google-only link).

Now I'm interested in renewing the OT for M115, but wondered if the fact that the OT wasn't effectively used on M113-M114 (nor before, tbh) could be considered as a gap in the OT, and hence the renewal won't be considered as extending <https://www.chromium.org/blink/launching-features/#origin-trials> beyond the 6 milestone initial limit.  Thoughts?

On Fri, Jan 6, 2023 at 11:13 AM Yoav Weiss <yoavwe...@chromium.org> wrote:

    Update: We're bumping the experimentation from M109 to M110 (till
    M113), to align with partner timelines (and avoid them
    rediscovering bugs fixed in M109).

    On Wed, Nov 30, 2022 at 3:16 PM Mike Taylor
    <miketa...@chromium.org> wrote:

        LGTM to experiment from M109 to M112.

        On 11/30/22 9:01 AM, Yoav Weiss wrote:


                Contact emails

        yoavwe...@chromium.org


                Explainer


        https://github.com/WICG/soft-navigations#soft-navigations
        <https://bit.ly/soft-navigation>


                Specification


        Not yet. I want to use the OT's feedback to assess the
        solution's viability.


                Summary

        Exposes the (experimental) soft navigation heuristics
        <https://github.com/WICG/soft-navigations#soft-navigations>
        to web developers, using both PerformanceObserver and the
        performance timeline.


                Blink component

        Blink>PerformanceAPIs
        
<https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EPerformanceAPIs>


                TAG review

        Not yet.


                TAG review status

        Not yet.


                Risks



                Interoperability and Compatibility



        /Gecko/: No signal for now. Will file once feedback confirms
        viability.

        /WebKit/: No signal for now. Will file once feedback confirms
        viability.

        /Web developers/: Strong
        <https://github.com/WICG/proposals/issues/71#issuecomment-1325856231>
        support
        <https://twitter.com/yoavweiss/status/1575191332775026688>!

        /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

        N/A



                Ongoing technical constraints

        None.



                Debuggability



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

        No


                Is this feature fully tested by web-platform-tests
                
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?

        Yes
        
<https://wpt.fyi/results/soft-navigation-heuristics?label=experimental&label=master&aligned&view=subtest>!


                Flag name

        SoftNavigationHeuristics


                Requires code in //chrome?

        False


                Tracking bug

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


                Estimated milestones

        OriginTrial desktop last        112
        OriginTrial desktop first       109

        OriginTrial Android last        112
        OriginTrial Android first       109

        OriginTrial webView last        112
        OriginTrial webView first       109



                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


        This intent message was generated by Chrome Platform Status
        <https://chromestatus.com/>.
-- 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+unsubscr...@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
        
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAL5BFfUb_Gn_5gGy8SnChg5KH2JN57Gv0NhnHN7Q_kH0Aa17CQ%40mail.gmail.com?utm_medium=email&utm_source=footer>.



--
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+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/5493d797-cfa3-2b84-9047-2488c2c46fb0%40chromium.org.

Reply via email to