Re: [csswg-drafts] [css-view-transitions-2] Figure out a way to make hit-testing work on live (new) elements during a view transition (#10930)

`pointer-events: forward` on the `::new` to forward to the original element seems very reasonable and straightforward.

But:

1. It won’t entirely solve the “main hallmark of identifying a view transition” issue though, as the `::view-transition-new` is obscured by the `::view-transition-old` in the tree while they fade in/out. So the `::view-transition-old` would still capture the clicks.
2. It’s a property value that would only do something on `::view-transition-new`, which seems a bit weird.

To work around the first issue, authors need to hide the `::view-transition-old` and not animate the `::view-transition-new` which only works when the old and new are the same _(modulo its size)_.

Perhaps we could do it all in one swoop, in which authors declare _“something”_ to indicate that only the new should be captured (shown?) and that pointer events (via the group?) should be forwarded to the new state element? Something like `view-transition-tbd: only-new`?

-- 
GitHub Notification of comment by bramus
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10930#issuecomment-2981373113 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 17 June 2025 18:18:02 UTC