Suggestion. pointer-events: disabled
Nobody has claimed this yet.
- Dominant language
- Bikeshed
- Stars
- 4.9k
- Forks
- 816
- PR merge metrics
- PR metrics pending
Description
Or some similar property value name.
disabled would mean no events at all. No event from ancestor elements. No :hover behaviour either. Unreactive.
none means that pointer events "see through" the element and just start their bubble and hover behaviour from the parentNode.
For some applications, you just want an element to be unreactive. Similar to adding the very first listener and calling stopImmediatePropagation on the event.
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 issue #4499 and the existing CSS pointer-events definition; compare the proposed disabled behavior with the current none behavior described in the issue. No implementation file or test is named, so done would require an agreed specification change for a value that suppresses pointer events and hover behavior, including its interaction with ancestor elements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100