- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 17 Jul 2023 10:21:05 +0000
- To: public-css-archive@w3.org
For the purpose of the F2F, summarizing current thinking: To maintain consistency with other CSS features, the idea is to have a new rule, currently called `@auto-view-transitions`, which can contain declarations that indicate to the UA the conditions in which view-transitions are to be automatically/declaratively performed (as opposed to programmatically as in vt-1). Initially, this rule would only have one possible declaration: `same-origin: enabled | disabled` (disabled by default). If enabled in both sides, a same-origin navigation would trigger an automatic view transition. See [current spec draft](https://drafts.csswg.org/css-view-transitions-2/#auto-view-transition-rule). Note that this value is read at exactly one point in both documents: - At the old document, when a same-origin navigation is about to be committed - At the new document, when there is a pending view-transition from the previous document and the first frame after navigation is about to be rendered. Main purpose of the discussion is to figure out if this syntax is optimal, e.g. is using `same-origin` as the property name tells the right story. -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8048#issuecomment-1637806513 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 17 July 2023 10:21:06 UTC