normative spec changes do not always end up as issues filed with browsers
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 202
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
See remarks of @marcoscaceres here: https://github.com/w3c/input-events/pull/149
Is there anything we can do to improve the browser internal communications?
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 remarks from @marcoscaceres in the linked input-events pull request #149, then compare them with this issue's question about browser communication. The work is not defined until the task force agrees on a concrete process or change and how successful browser issue filing will be measured.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100