- From: vmpstr via GitHub <noreply@w3.org>
- Date: Tue, 17 Jun 2025 17:24:13 +0000
- To: public-css-archive@w3.org
I'd like to explore this further. One of the main hallmarks of identifying a view transition is that you don't get any hover effects or pointer changes (say over text) when hovering over a view transition pseudo that represents some element. That seems bad. It becomes more of an issue for long running animations or animations in a paused state driven by something like a scroll timeline or other user interactions. I suspect it also will become more of an issue in scoped transitions if the prevalence of small scoped transitions increases. I'm thinking that a pattern could be something like setting `pointer-events: none` on the old pseudo, and `pointer-events: forward` (as a strawman) on the new pseudo which enables forwarding pointer events from that pseudo to the element being represented. This would map the event to the coordinates of the new element and let it capture and bubble starting at the actual element. One downside is that, as far as I know, `pointer-events: forward` would only be applicable to `::view-transition-new`. One other possibility is it would be something like `pointer-events: forward(#foo)` where `#foo` is an element id to which to forward events. This could apply in more cases, but opens the door to security considerations (e.g. clickjacking). Yet another possibility is to have `pointer-events: auto` do the magic thing on `::view-transition-new`, but of course without another keyword this precludes the possibility of actually handling the click on the new pseudo without forwarding. /cc @bramus -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10930#issuecomment-2981193702 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 17:24:14 UTC