(feature) EventTarget API on host elements
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, react-native
- Domain
- mobile-dev
Research direction
Start by reading the existing EventTarget, addEventListener, and removeEventListener discussion, then review the event emitters, traversal APIs, and React Native event system mentioned in the issue. Determine whether the implementation should be a polyfill or integrated into React Native, including W3C-compatible timing, payloads, and capture/bubble behavior; done means host elements support the API consistently.
Written by the indexing model from the issue text.
Description
Describe the feature request
The EventTarget interface is implemented by objects that can receive events and may have listeners for them. Native does not currently support this API on host elements.
Previously we had introduced a prototype implementation of addEventListener and removeEventListener in React Native, but it was removed as it needs to be reimplemented properly and integrated with broader changes to React Native. For example, the events need to conform to W3C standards in terms of timing and event payload.
In the meantime, we may be able to polyfill this API using event emitters and the new traversal APIs, which would allow us to emulate capture/bubble phases of events. But, ideally we'd build this into React Native given it would be more performant and there is already an existing event system.
- Dominant language
- JavaScript
- Stars
- 3.6k
- Forks
- 206
- PR merge metrics
- No merged PRs in 30d
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.
More from react/react-strict-dom
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
react/react-strict-dom#467 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
react/react-strict-dom#465 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
react/react-strict-dom#520 ·
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
react/react-strict-dom#505 · 2 reactions ·
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
react/react-strict-dom#491 · 4 comments ·
All issues in react/react-strict-dom
Similar issues
-
awaiting triage bug Causes friction Hop Gui P1 P2 Transforms
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
georgestephanis/p2026#40 ·
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Margaret-Petersen/food-delivery-app-clone-react-native#1981 ·