input event should use InputEvent
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 9.4k
- Forks
- 3.2k
- Avg merge
- 3d 9h
- Merged PRs (30d)
- 38
Description
http://w3c.github.io/editing/input-events.html defines a new InputEvent type that it clearly intends to be used for the HTML input event defined in https://html.spec.whatwg.org/#event-input. However, it never defines the actual procedure by which these events are created or fired, or how their initialization values are determined. (It has some vague stuff like "A user agent MUST dispatch this event immediately after the DOM has been updated." but that clearly doesn't fit into the existing lifecycle; compare it to the spec's existing "Queue a task to fire a simple event that bubbles named input at the input element.") Furthermore, HTML currently says to dispatch a plain ol' Event.
It seems, based on blink-dev, there is public support for this change. We should update HTML.
See also #601.
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 HTML Standard's event-input section, compare its plain Event dispatch procedure with the InputEvent definition in the linked Input Events specification, and review related issue #601. Done means HTML specifies how the InputEvent is created, initialized, and fired for the input event.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100