Event firing does not specify attributes
Open
Nobody has claimed this yet.
bug
- Dominant language
- HTML
- Stars
- 718
- Forks
- 228
- PR merge metrics
- No merged PRs in 30d
Description
WebDriver references the DOM concept to fire an event but does not supply the eventConstructor argument, meaning we don’t specify which attributes are meant to be set.
We could follow the HTML approach and define a short set of steps on how to fire synthetic events, then populate a few shorthands to those.
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 by reading the linked DOM “fire an event” concept and the HTML “fire a synthetic mouse event” approach. Define the short synthetic-event steps and event shorthands described in the issue so the event attributes to set are specified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100