[css-view-transitions-1] The ability for authors to re-enable pointer events
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
I'm currently trying to make the below animation work using the view transitions api.
As you can see, the 'Subscribe with Google Pay' button is not clickable until the 'More payment options' link has appeared.
The same is true for the 'yearly billing' checkbox as well. This is because the modal itself is being resized as part of the same view transition.
The 'More payment options' link has a long delay for demonstration purposes. I intend to shorten the delay in the final result, so creating a second view transition for just that button isn't really an option either.
https://github.com/user-attachments/assets/0e3948af-759f-41af-9a67-ab7ca8315ec5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CSS View Transitions Level 1 specification and the animation example linked in the issue, focusing on how pointer events are handled during transitions. The issue does not name files or tests; done would require an agreed specification change that lets authors control when pointer events are re-enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100