Re: [csswg-drafts] [css-view-transitions-1] The ability for authors to re-enable pointer events (#11596)

Hey y’all! I just wanted to boost this issue, as it's something I’ve run into a few times in my own work. Whenever an interactive element like a button/link is part of a view transition, I expect to be able to click it even during the transition, but because hit-testing is disabled, the element is completely inert for folks using a pointer device. As a result, it produces pretty confusing UX where a button can be seen but not clicked. The only solution right now is to remove the `view-transition-name`, which in many cases causes it to get hidden behind another element that is transitioning (so, the button can be clicked but not seen).

I think @noamr’s suggestion to forward the events to the element lending its pixels to `::view-transition-new` is a great idea. I think it should be the default, since I suspect most developers using View Transitions won’t get deep enough to fully understand what's going on here or why the clicks aren't working.

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


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

Received on Friday, 20 February 2026 15:11:56 UTC