pagereveal event
#303
Assignees
Labels
from: Google
Proposed, edited, or co-edited by Google.
position: support
topic: css
Spec relates to CSS (Cascading Style Sheets)
topic: events
Spec relates to DOM events
venue: WHATWG HTML Workstream
Comments
|
Friendly ping as Chromium is getting ready to send out an intent to ship for this and we'd like to get a signal from WebKit before we do so. |
|
FYI: we've sent out an intent-to-ship for this on blink-dev targeting M123. |
nt1m
added
topic: css
|
I'm planning to mark this as supportive in a week if there are no objections. The standard is reasonable, and @mattwoodrow is implementing it. |
github-project-automation
bot
moved this to Unscreened
in Standards Positions Review Backlog
nt1m
moved this from Unscreened
to Position identified
in Standards Positions Review Backlog
github-project-automation
bot
moved this from Position identified
to Done
in Standards Positions Review Backlog
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
WebKittens
@nt1m
Title of the spec
HTML: pagereveal event
URL to the spec
https://html.spec.whatwg.org/#pagerevealevent
URL to the spec's repository
https://github.com/whatwg/html/
Issue Tracker URL
No response
Explainer URL
https://github.com/WICG/view-transitions/blob/main/cross-doc-explainer.md#javascript-api
TAG Design Review URL
w3ctag/design-reviews#851
Mozilla standards-positions issue URL
mozilla/standards-positions#677
WebKit Bugzilla URL
No response
Radar URL
No response
Description
This event is a dependency of the CSS View Transitions Level 2 spec (Webkit Position Issue).
There was significant review and technical debate on whatwg/html#9315 and spec changes were accepted into HTML.
The TAG review and Explainer both point to the larger CSS View Transitions Level 2 items which included this event as part of the design (then called
reveal).The text was updated successfully, but these errors were encountered: