- From: Noam Rosenthal via GitHub <sysbot+gh@w3.org>
- Date: Mon, 05 Jun 2023 16:40:05 +0000
- To: public-css-archive@w3.org
I wonder if instead of addressing this as a view-transitions problem, we should look at this from the point of view of `a` elements. The same way we have the `:active` and `:target` pseudo-classes, we could have `:next` and `:previous` (we can bikeshed the names, can be `:outgoing` and `:incoming`). When a link is clicked, it would be the `:outgoing` or `:next` link. Links that would lead to the previously displayed URL would be `:incoming` or `:previous`. So given a list of mini-posters that goes to a maxi-poster: ```css a.miniposter:is(:next, :previous) { view-transition-name: poster; } h1.maxiposter { view-transition-name: poster; } ``` As a side-benefit, this would also let us curate cross-document view-transitions based on incoming URLs: ```css html:has(a#home:previous) { // customize transition based on the previous URL being "home" } ``` -- GitHub Notification of comment by noamr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8209#issuecomment-1577127121 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 5 June 2023 16:40:07 UTC