Safari Desktop: When aborting a composition after pressing a dead key (e.g. `^`) in oncompositionend event.data will have `""` while `"^"` is expected
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 202
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
With aborting I mean pressing a dead key (composition starts) and then click somewhere else (composition is implicitly ended - oncompositionend is called).
However since the native behavior of contenteditable would leave the "^" in the DOM after cancelling, I'd expect the event.data in oncompositionend also have "^", which is not the case on Desktop Safari.
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 linked reproduction at https://w3c.github.io/editing/repros/505.html and verify the behavior in Desktop Safari. Compare the native contenteditable result with the oncompositionend event.data value; done means determining whether the reported empty value differs from the expected dead-key character and documenting the result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100