Event data is wrong due to interface object not being exposed originally
Open
Nobody has claimed this yet.
browser:multiple
data:api
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
The data in https://github.com/mdn/browser-compat-data/pull/11791 is likely wrong for the reasons outlined in https://github.com/mdn/browser-compat-data/pull/11881#issuecomment-896595350.
https://trac.webkit.org/changeset/94493/webkit added window.CompositionEvent and that happened in Chrome 15, but instances of the event interface were probably supported before that.
cc @vinyldarkscratch
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
Review PR 11791 and the comment on PR 11881 first, then compare their claims with WebKit changeset 94493 and the stated Chrome 15 timing. Done means the CompositionEvent compatibility data distinguishes exposing the interface from earlier support for event instances.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100