Contact emails bo...@chromium.org, khushalsa...@chromium.org, nrosent...@chromium.org, vmp...@chromium.org
Explainer https://github.com/WICG/view-transitions/blob/main/cross-doc-explainer.md (See https://github.com/whatwg/html/issues/9315 for design discussion around this event specifically) Specification https://drafts.csswg.org/css-view-transitions-2/#pagerevealevent Summary The `firstrender` event is fired on a Document's window object at the first render opportunity after a Document is: initially loaded, restored from the back-forward cache, activated from a prerender. It can be used by a page author to setup a page entry UX - such as a ViewTransition from a previous state. This feature is split out from the larger ViewTransition-on-Navigation project. Blink component Blink>ViewTransitions <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3EViewTransitions> Motivation This event enables authors to make last-minute DOM changes once a document is ready to be presented but before it is rendered. In particular, this enables an author to setup their style for a ViewTransition, if one is available, from a single convenient place. Without it, authors would have to do this from a `requestAnimationFrame` and also remember to add listen to `pageshow.persisted` to handle the BFCache case, which is error prone. This event is also how a cross-document ViewTransition object is passed into the incoming Document. Initial public proposal https://github.com/whatwg/html/issues/9315 Search tags transition <https://chromestatus.com/features#tags:transition>, firstrender <https://chromestatus.com/features#tags:firstrender>, reveal <https://chromestatus.com/features#tags:reveal>, event <https://chromestatus.com/features#tags:event>, viewtransition <https://chromestatus.com/features#tags:viewtransition> TAG review None TAG review status Pending Risks Interoperability and Compatibility None *Gecko*: No signal *WebKit*: No signal *Web developers*: No signals *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? None Debuggability None Is this feature fully tested by web-platform-tests <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md> ? No Flag name on chrome://flags None Finch feature name None Non-finch justification None Requires code in //chrome? False Tracking bug https://crbug.com/1466250 Estimated milestones No milestones specified Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5205586941837312 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/f0f76584-ea3f-43ab-946c-b920fc064344n%40chromium.org.
