Clarify how CompositionEvents should be initialized
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 48
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
Currently the language around firing compositionstart/end events is just:
Fire an event named compositionstart/compositionend at editContext using CompositionEvent.
But this doesn't make it clear how the view and data attributes should be initialized. There is the table in the UI Events spec, but that seems to only apply to non-EditContext composition events on elements. Probably the EditContext spec should be explicit about this.
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 EditContext wording for firing compositionstart and compositionend, then compare the UI Events CompositionEvent table linked in the issue. Clarify how the view and data attributes are initialized for EditContext events; done when the specification states this explicitly without relying on assumptions about non-EditContext events.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100