Intent to Ship: 'pagereveal' event
David Bokan
Contact emails
bo...@chromium.org, khusha...@chromium.org, nrose...@chromium.org, vmp...@chromium.orgExplainer
https://github.com/WICG/view-transitions/blob/main/cross-doc-explainer.mdSpecification
https://html.spec.whatwg.org/#revealDesign docs
https://github.com/WICG/view-transitions/blob/main/cross-doc-explainer.md
Summary
The `pagereveal` 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, or activated from a prerender. It can be used by a page author to set up a page entry UX - such as a ViewTransition from a previous state. This feature is split out from the larger Cross Document View Transition project.
Blink component
Blink>ViewTransitionsSearch tags
transition, firstrender, reveal, event, viewtransitionTAG review
https://github.com/w3ctag/design-reviews/issues/851TAG review status
Issues addressedRisks
Interoperability and Compatibility
This is a new event so shouldn't have any compatibility risks. Usual interop risk of other engines not adopting it exists but this should be low since it's had input and discussion[1] from engineers of both WebKit and Mozilla and is a dependency of cross-document view transitions which has received a positive signal from at least Mozilla[2] (waiting to hear from Apple[3]). [1] https://github.com/whatwg/html/issues/9315 [2] https://github.com/mozilla/standards-positions/issues/677
[3] https://github.com/WebKit/standards-positions/issues/302
Gecko: Positive (https://github.com/mozilla/standards-positions/issues/677) See: https://github.com/mozilla/standards-positions/issues/677#issuecomment-1904541389
WebKit: No signal (https://github.com/WebKit/standards-positions/issues/303) Awaiting response.
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?
No
Debuggability
None
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
YesThis is a standard HTML event applicable to all platforms
Is this feature fully tested by web-platform-tests?
YesFlag name on chrome://flags
chrome://flags/#enable-experimental-web-platform-featuresFinch feature name
PageRevealEventRequires code in //chrome?
FalseTracking bug
https://crbug.com/1466250Estimated milestones
| Shipping on desktop | 123 |
| DevTrial on desktop | 120 |
| Shipping on Android | 123 |
| DevTrial on Android | 120 |
| Shipping on WebView | 123 |
Anticipated spec changes
Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (e.g. links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (e.g., changing to naming or structure of the API in a non-backward-compatible way).
NoneLink to entry on the Chrome Platform Status
https://chromestatus.com/feature/5205586941837312Links to previous Intent discussions
Intent to prototype: https://groups.google.com/a/chromium.org/d/msgid/blink-dev/f0f76584-ea3f-43ab-946c-b920fc064344n%40chromium.org
Domenic Denicola
Contact emails
bo...@chromium.org, khusha...@chromium.org, nrose...@chromium.org, vmp...@chromium.orgExplainer
https://github.com/WICG/view-transitions/blob/main/cross-doc-explainer.mdSpecification
https://html.spec.whatwg.org/#revealDesign docs
https://github.com/WICG/view-transitions/blob/main/cross-doc-explainer.mdSummary
The `pagereveal` 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, or activated from a prerender. It can be used by a page author to set up a page entry UX - such as a ViewTransition from a previous state. This feature is split out from the larger Cross Document View Transition project.
Blink component
Blink>ViewTransitionsSearch tags
transition, firstrender, reveal, event, viewtransitionTAG review
https://github.com/w3ctag/design-reviews/issues/851Note: TAG review was for Cross-Document View Transitions which included this event as a piece. I asked TAG whether they'd like to do a separate review but didn't receive a response.
TAG review status
Issues addressedRisks
Interoperability and Compatibility
This is a new event so shouldn't have any compatibility risks. Usual interop risk of other engines not adopting it exists but this should be low since it's had input and discussion[1] from engineers of both WebKit and Mozilla and is a dependency of cross-document view transitions which has received a positive signal from at least Mozilla[2] (waiting to hear from Apple[3]). [1] https://github.com/whatwg/html/issues/9315 [2] https://github.com/mozilla/standards-positions/issues/677
[3] https://github.com/WebKit/standards-positions/issues/302
Gecko: Positive (https://github.com/mozilla/standards-positions/issues/677) See: https://github.com/mozilla/standards-positions/issues/677#issuecomment-1904541389
WebKit: No signal (https://github.com/WebKit/standards-positions/issues/303) Awaiting response.
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?
No
Debuggability
None
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?
YesThis is a standard HTML event applicable to all platforms
Is this feature fully tested by web-platform-tests?
Yes
--
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/CANMmsAvhWAzVrHCudjLgQRtePgqEHucNqb27Wkn9r4dCKeUTWg%40mail.gmail.com.
David Bokan
Can you un-tentative these tests?
Christian Biesinger
Contact emails
bo...@chromium.org, khusha...@chromium.org, nrose...@chromium.org, vmp...@chromium.orgExplainer
https://github.com/WICG/view-transitions/blob/main/cross-doc-explainer.mdSpecification
https://html.spec.whatwg.org/#revealDesign docs
https://github.com/WICG/view-transitions/blob/main/cross-doc-explainer.mdSummary
The `pagereveal` 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, or activated from a prerender. It can be used by a page author to set up a page entry UX - such as a ViewTransition from a previous state. This feature is split out from the larger Cross Document View Transition project.
"Note that this event is different from
pageshow as a newly initialized document fires pageshow is only once the document is fully loaded."David Bokan
Mike Taylor
LGMT2 - no concerns about lack of a response from TAG.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAM0wra_Yjbyiv9Ezi_d%2BrWgutSTwcAVGwBJPxkkDCQptuozqEg%40mail.gmail.com.
Chris Harrelson
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/093ddfbf-486b-42fd-aecb-1e86b6970586%40chromium.org.