-
Notifications
You must be signed in to change notification settings - Fork 195
Bump @mdn/browser-compat-data from 5.6.21 to 5.6.22 #2409
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bump @mdn/browser-compat-data from 5.6.21 to 5.6.22 #2409
Conversation
Bumps [@mdn/browser-compat-data](https://github.com/mdn/browser-compat-data) from 5.6.21 to 5.6.22. - [Release notes](https://github.com/mdn/browser-compat-data/releases) - [Changelog](https://github.com/mdn/browser-compat-data/blob/main/RELEASE_NOTES.md) - [Commits](mdn/browser-compat-data@v5.6.21...v5.6.22) --- updated-dependencies: - dependency-name: "@mdn/browser-compat-data" dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]>
|
Complete this checklist for every
After merging, do these steps: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks correct to me, but there's an… interesting and pervasive change to the data.
The way BCD assumes support across browsers (known as mirroring, e.g., from Chrome to Edge or Firefox to Firefox for Android) has changed (see mdn/browser-compat-data#24155). This change exposes uncertainty that was previously hidden. The following features now have ranged statuses (which were previously unranged):
- background-size
- display-table
- dominant-baseline
- opacity-svg
The following features already had ranged headline statuses:
- output
- sourcemap-header
- wasm-mutable-globals
I think we ought to contribute fixes upstream to prevent ranged headline statuses (ranges on per key statuses are very numerous and would be a large effort), but I don't think this should block merging.
| baseline_low_date: ≤2020-07-28 | ||
| baseline_high_date: ≤2023-01-28 | ||
| support: | ||
| chrome: "21" | ||
| chrome_android: "25" | ||
| edge: "12" | ||
| firefox: ≤72 | ||
| firefox_android: "79" | ||
| firefox_android: ≤79 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Newly ranged. Not a regression per se, but uncertainty has been added.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just opened mdn/browser-compat-data#25356 to replace this range with a specific version.
| baseline_low_date: 2020-07-28 | ||
| baseline_high_date: 2023-01-28 | ||
| baseline_low_date: ≤2020-07-28 | ||
| baseline_high_date: ≤2023-01-28 | ||
| support: | ||
| chrome: ≤80 | ||
| chrome_android: "80" | ||
| edge: "80" | ||
| chrome_android: ≤80 | ||
| edge: ≤80 | ||
| firefox: ≤72 | ||
| firefox_android: "79" | ||
| firefox_android: ≤79 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Newly ranged. Not a regression per se, but uncertainty has been added.
| baseline_low_date: 2020-07-28 | ||
| baseline_high_date: 2023-01-28 | ||
| baseline_low_date: ≤2020-07-28 | ||
| baseline_high_date: ≤2023-01-28 | ||
| support: | ||
| chrome: ≤80 | ||
| chrome_android: "80" | ||
| edge: "80" | ||
| chrome_android: ≤80 | ||
| edge: ≤80 | ||
| firefox: ≤72 | ||
| firefox_android: "79" | ||
| firefox_android: ≤79 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Newly ranged. Not a regression per se, but uncertainty has been added.
| baseline_low_date: 2020-07-28 | ||
| baseline_high_date: 2023-01-28 | ||
| baseline_low_date: ≤2020-07-28 | ||
| baseline_high_date: ≤2023-01-28 | ||
| support: | ||
| chrome: ≤80 | ||
| chrome_android: "80" | ||
| chrome_android: ≤80 | ||
| edge: ≤80 | ||
| firefox: ≤72 | ||
| firefox_android: "79" | ||
| firefox_android: ≤79 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Newly ranged. Not a regression per se, but uncertainty has been added.
| # edge: "79" | ||
| # firefox: ≤72 | ||
| # firefox_android: "79" | ||
| # firefox_android: ≤79 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change doesn't make sense to me- shouldn't it be ≤72?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It makes sense because Fx Android 69-78 have been skipped. https://github.com/mdn/browser-compat-data/blob/8d1d3706247e66603e19205fcdd7852f956b35e3/browsers/firefox_android.json#L445
Bumps @mdn/browser-compat-data from 5.6.21 to 5.6.22.
Release notes
Sourced from
@mdn/browser-compat-data's releases.Changelog
Sourced from
@mdn/browser-compat-data's changelog.Commits
33022c8Release v5.6.22 (#25304)87871efSafari 18 supports mixed type parameters in CSS color types (#25293)1697611Chrome 52 / Firefox 34 / Safari 9 supportfont-variant: none(#25328)4c9f851[css.selectors.attribute] Add WebKit bug for case‑sensitive modifier (#25331)15e7096Chrome Android also supports::details-content(#25342)a56408eBump@ddbeck/mdn-content-inventoryfrom 0.2.20241205 to 0.2.20241206 (#25341)8cb3cf8Chrome 1 supportedbackground-position: bottom/center/left/right/top(#25283)809bd95Chromium 130 supportstext-wrap-modeCSS property (#25333)1ddfce2Chrome 115 added HTMLFencedFrameElement.sandbox (#25227)4d0aa91Chromium 130 supportstext-wrap: stable(#25334)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)