Suspect differences between IE and Edge support
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
https://github.com/mdn/browser-compat-data/pull/23791 was a case where there was an IE version, but Edge was set to mirror, resulting in Edge 79. This is probably correct in some case, but there are probably more errors of this sort.
comm -23 <(npm run traverse -- -b edge -f mirror | sort) <(npm run traverse -- -b ie -f false -f null | sort) produces this list for review:
- api.BeforeUnloadEvent (https://github.com/mdn/browser-compat-data/pull/23797)
- api.BeforeUnloadEvent.returnValue (https://github.com/mdn/browser-compat-data/pull/23797)
- api.Document.releaseCapture
- api.IDBObjectStore.autoIncrement
- api.IDBObjectStore.openKeyCursor
- api.Navigator.taintEnabled (tested; data is correct)
- api.Window.beforeunload_event.event_returnvalue_activation
- api.Window.showModalDialog
- css.properties.overflow-x.auto (https://github.com/mdn/browser-compat-data/pull/23798)
- css.properties.overflow-y.auto (https://github.com/mdn/browser-compat-data/pull/23798)
- css.properties.overflow.auto (https://github.com/mdn/browser-compat-data/pull/23798)
- css.properties.text-combine-upright.digits
- css.selectors.placeholder-shown
- html.elements.iframe.sandbox.allow-same-origin
- html.elements.link.rel.alternate_stylesheet
- html.elements.link.rel.prerender
- html.elements.rb
- html.elements.rp (https://github.com/mdn/browser-compat-data/pull/23791)
- html.elements.rt (https://github.com/mdn/browser-compat-data/pull/23791)
- html.elements.source.height
- html.elements.source.width
- html.elements.wbr (https://github.com/mdn/browser-compat-data/pull/23804)
- svg.elements.circle.fill
- svg.elements.ellipse.fill
- svg.elements.path.fill
- svg.elements.pattern.href
- svg.elements.polygon.fill
- svg.elements.polyline.fill
- svg.elements.rect.fill
- svg.elements.text.fill
- svg.elements.textPath.fill
- svg.elements.tspan.fill
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 npm run traverse command in the issue and compare its IE and Edge output. Review the unchecked entries, including the listed API, CSS, HTML, and SVG paths, against the project’s compatibility data. Done means each discrepancy has been verified and the relevant data is corrected or confirmed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100