LGTM2

On 8/16/23 6:38 PM, Chris Harrelson wrote:
LGTM1 to ship once the spec PR has landed.

On Mon, Aug 14, 2023 at 7:50 AM 'Khushal Sagar' via blink-dev <blink-dev@chromium.org> wrote:


            Contact emails

    khushalsa...@google.com, liuwill...@google.com, hvanops...@google.com


            Explainer

    https://github.com/WICG/view-transitions/blob/main/default-ua-transitions.md


            Specification

    https://github.com/whatwg/html/pull/9579


            Summary

    Smooth visual transitions as users navigate on the web can lower
    cognitive load by helping users stay in context. However, the user
    experience is bad if both the site author and the UA add these
    transitions: the transitions may conflict and cause confusion for
    the user. This API avoids such cases to ensure only one visual
    transition is executed at a time. The API adds a boolean on
    `PopStateEvent` and `NavigateEvent` to indicate whether the UA has
    executed a visual transition for this navigation. Authors can use
    this to skip their custom transition.



            Blink component

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


            TAG review

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


            TAG review status

    Issues addressed


            Risks



            Interoperability and Compatibility

    This feature is a progressive enhancement. In the absence of the
    feature, the author has to either conservatively assume there is a
    UA transition (and not do a custom transition) or risk visual
    glitches from double transition. As such there is no interop risk.



    /Gecko/: No signal
    (https://github.com/mozilla/standards-positions/issues/783)

    /WebKit/: Positive
    (https://github.com/WebKit/standards-positions/issues/176)

    /Web developers/: Strongly positive Issues like this:
    
https://stackoverflow.com/questions/66867737/iphone-safari-detect-swipe-navigation.
    This is likely to happen more as authors can now use
    ViewTransitions to add custom transitions in SPAs.

    /Other signals/:


            Activation

    None



            Security

    None. The API is limited to same-document navigations.



            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?

    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
            
<https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>?

    No. WPTs assert that the attribute is present but not the value.
    By design, when this is set is left to the UA.


            Flag name on chrome://flags



            Finch feature name

    None


            Non-finch justification

    None


            Requires code in //chrome?

    False


            Estimated milestones

    Shipping on desktop         118

    Shipping on Android         118

    Shipping on WebView         118



            Anticipated spec changes

    None



            Link to entry on the Chrome Platform Status

    https://chromestatus.com/feature/5204831477694464


            Links to previous Intent discussions

    Intent to prototype:
    
https://groups.google.com/a/chromium.org/g/blink-dev/c/UJMYZXoSQ4A/m/OkIvKVtlAAAJ

    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/CAMLuWUyhcTn1%3D%3DxfV0i5tyLS-APwqfDpetBstDie_4uMyxB1xQ%40mail.gmail.com
    
<https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMLuWUyhcTn1%3D%3DxfV0i5tyLS-APwqfDpetBstDie_4uMyxB1xQ%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/CAOMQ%2Bw_fDO1UDKkjDk1tGNm-_Y02mxdFh7i45RrboAAkbK0_cA%40mail.gmail.com <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOMQ%2Bw_fDO1UDKkjDk1tGNm-_Y02mxdFh7i45RrboAAkbK0_cA%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/cf5ee66c-e745-4cce-8352-f09b9f518043%40chromium.org.

Reply via email to