Is the experiment 103 to 106 or 104 to 107. Joe Medley | Technical Writer, Chrome DevRel | [email protected] | 816-678-7195 *If an API's not documented it doesn't exist.*
On Mon, Jun 13, 2022 at 8:49 AM 'Hannah Van Opstal' via blink-dev < [email protected]> wrote: > Hi Nicola, > > This experimentation is still for the same-origin case. > The difference is in the shape of the API. The first intent was approved > for the API when it was using Viz. With Viz Shared Element Transitions, we > did an origin trial where we received some feedback that led us to change > it to use the renderer. So this new intent would be intended for the newer > shape - i.e. renderer SET. > > Please let me know if we can provide any more details. > > Hannah > > > > > > On Mon, Jun 13, 2022 at 7:16 AM Nicola Tommasi <[email protected]> > wrote: > >> Hi API owners, >> >> This intent seems to be already approved in the past for same-origin >> experimentation, is this launch intended for the cross-origin case?If not, >> what's exactly in the scope for this particular launch? >> >> Thanks, >> Nicola >> >> On Thursday, June 9, 2022 at 8:35:23 AM UTC Yoav Weiss wrote: >> >>> LGTM to experiment M103-M106 >>> >>> Thanks for working on this! I'm super excited about the possibilities >>> this will open!! >>> >>> On Wed, Jun 8, 2022 at 9:27 PM Khushal Sagar <[email protected]> >>> wrote: >>> >>>> >>>> >>>> On Wed, Jun 8, 2022 at 3:11 PM Khushal Sagar <[email protected]> >>>> wrote: >>>> >>>>> Contact [email protected], [email protected], >>>>> [email protected] >>>>> >>>>> Explainer >>>>> https://github.com/WICG/shared-element-transitions/blob/main/explainer.md >>>>> >>>>> Specification >>>>> https://tabatkins.github.io/specs/css-shared-element-transitions >>>>> >>>>> Design docs >>>>> >>>>> https://github.com/WICG/shared-element-transitions/blob/main/explainer.md >>>>> >>>>> Summary >>>>> >>>>> Shared Element Transitions is a proposal for a new script API that >>>>> allows a simple set of transitions in both Single-Page Applications (SPAs) >>>>> and Multi-Page Applications (MPAs). This feature enhances the visual >>>>> polish >>>>> of pages without requiring a large development effort from developers to >>>>> make transitions look nice. By selecting from a set of user-agent >>>>> implemented transition effects, the developers can achieve a polished >>>>> transition look with minimal effort. >>>>> >>>>> >>>>> Blink componentBlink>Animation >>>>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EAnimation> >>>>> >>>>> TAG reviewhttps://github.com/w3ctag/design-reviews/issues/631 >>>>> >>>>> TAG review statusPending >>>>> >>>>> Link to origin trial feedback summary >>>>> https://docs.google.com/spreadsheets/d/1x7IueF5_Ds7oyihAV1DB3yzR4f-SbPcKc5DMvBzg-nM/edit#gid=2085648173 >>>>> >>>>> Risks >>>>> >>>>> Interoperability and Compatibility >>>>> >>>>> Low. As a new feature, the risk here is that other browsers do not >>>>> implement it, but since this is a progressive enhancement, sites should be >>>>> able to drop usage of the feature easily in browsers where it is not >>>>> supported. >>>>> >>>>> *Gecko*: No signal >>>>> >>>>> *WebKit*: No signal >>>>> >>>>> *Web developers*: Strongly positive >>>>> Interest and developer experiments with the API: >>>>> >>>>> https://twitter.com/jaffathecake/status/1524782819431555074?t=itU6B0wo6SbjomGiSKLmGQ&s=19 >>>>> >>>>> https://www.reddit.com/r/webdev/comments/uyoit1/i_played_around_with_chromes_new_shared_element/ >>>>> >>>>> https://twitter.com/OliverJAsh/status/1530261401016705026?t=CXqW2yiIMbH6bLfn8ImINw&s=19 >>>>> >>>>> https://css-tricks.com/spas-shared-element-transitions-and-re-evaluating-technology/ >>>>> >>>>> *Other signals*: >>>>> >>>>> Ergonomics >>>>> >>>>> None. >>>>> >>>>> Activation >>>>> >>>>> Low. As with interop/compat risks, the difficulty stems from this >>>>> being a new feature without support in other browsers. A polyfill for the >>>>> SPA case would be beneficial, but it will not be possible to polyfill MPA >>>>> behavior. That said, dropping the customized transition should not impact >>>>> the usability of a site, fundamentally, so this can easily be dropped on >>>>> browsers that do not support the feature. >>>>> >>>>> Security >>>>> >>>>> The primary security constraint is ensuring isolation of graphics >>>>> resources from multiple origins. The design achieves that using Chromium's >>>>> Viz process similar to OOPIFs. >>>>> >>>>> See also the security and privacy self-review questionnaire that was >>>>> completed as part of the TAG review process: >>>>> https://github.com/WICG/shared-element-transitions/blob/main/security-privacy-questionnaire.md >>>>> >>>>> 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? >>>>> >>>>> >>>>> >>>>> Goals for experimentation >>>>> >>>>> Learning from the feedback from the previous OT, the API has been >>>>> updated to layer on top existing animation systems on the platform. This >>>>> allows the browser to provide a set of default transitions which >>>>> developers >>>>> can extensively customize. We want to learn that developers can easily >>>>> adopt this API and build the desired UX using the customization options >>>>> provided. >>>>> >>>>> Reason this experiment is being extended >>>>> Ongoing technical constraints >>>>> >>>>> None. >>>>> >>>>> Debuggability >>>>> >>>>> The feature can be debugged using standard tooling in devtools. >>>>> Specifically the animation panel can be used to pause and scrub through >>>>> the >>>>> default animations set by the browser. The pseudo DOM structure generated >>>>> by the UA can also be inspected and targeted, like other DOM elements, in >>>>> the style panel. >>>>> >>>>> Will this feature be supported on all six Blink platforms (Windows, >>>>> Mac, Linux, Chrome OS, Android, and Android WebView)?No >>>>> >>>>> Currently no support for Android WebView. This is WIP. >>>>> >>>>> Is this feature fully tested by web-platform-tests >>>>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> >>>>> ?Yes >>>>> >>>>> Flag nameDocumentTransition >>>>> >>>>> Requires code in //chrome?False >>>>> >>>>> Tracking bug >>>>> https://bugs.chromium.org/p/chromium/issues/detail?id=1328796 >>>>> >>>>> Estimated milestones >>>>> OriginTrial desktop last 107 >>>>> OriginTrial desktop first 104 >>>>> OriginTrial Android last 107 >>>>> OriginTrial Android first 104 >>>>> >>>> >>>> One fix, the last milestone for the OT is 106. So it's targeted for 3 >>>> milestones 104-106 (inclusive). The end date will be October 18, 2022. >>>> >>>> >>>>> >>>>> Link to entry on the Chrome Platform Status >>>>> https://chromestatus.com/feature/5193009714954240 >>>>> >>>>> Links to previous Intent discussionsIntent to prototype: >>>>> https://groups.google.com/a/chromium.org/g/blink-dev/c/7SMI3IklO4g/m/JS-JojxNAwAJ >>>>> >>>>> >>>>> 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 [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMLuWUy2%3DZk_C64CJjCjxKfKbH6XHEzTLO5cWd%3D_H6GUCzNAWg%40mail.gmail.com >>>> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAMLuWUy2%3DZk_C64CJjCjxKfKbH6XHEzTLO5cWd%3D_H6GUCzNAWg%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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADzDAdAgiq3HZE5gVgiEJVwO9EKO1ic%2BuW8%3DxXLGKfj0JAzWYw%40mail.gmail.com > <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CADzDAdAgiq3HZE5gVgiEJVwO9EKO1ic%2BuW8%3DxXLGKfj0JAzWYw%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 [email protected]. To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJUhtG-j9kHLyGZ0x%3D3XNfrEY7ez1JuZ%2B2arAW2ttz7N0jn3YA%40mail.gmail.com.
