Bump @mdn/browser-compat-data from 7.3.7 to 7.3.8#3881
Conversation
Bumps [@mdn/browser-compat-data](https://github.com/mdn/browser-compat-data) from 7.3.7 to 7.3.8. - [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@v7.3.7...v7.3.8) --- updated-dependencies: - dependency-name: "@mdn/browser-compat-data" dependency-version: 7.3.8 dependency-type: direct:development update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
|
Complete this checklist for every
After merging, do these steps: |
features/clear-site-data.yml.dist
Outdated
|
|
||
| status: | ||
| baseline: low | ||
| baseline: high |
There was a problem hiding this comment.
This should not advance and should probably regress. I've sent mdn/browser-compat-data#29333 upstream. I'll freeze this status and file an issue before merging.
There was a problem hiding this comment.
Agreed. Bug https://issues.chromium.org/issues/364634040 feels serious and should hold the feature back.
|
A bunch of features are advancing statuses in this upgrade. Here's a summary: low to high:
false to low |
captainbrosset
left a comment
There was a problem hiding this comment.
I'm OK with the large number of features progressing from baseline low to high. These features match what I see at https://developer.apple.com/documentation/safari-release-notes/safari-17-release-notes.
| # baseline: low | ||
| # baseline_low_date: 2025-09-15 | ||
| # support: | ||
| # chrome: "122" | ||
| # chrome_android: "122" | ||
| # edge: "122" | ||
| # firefox: "134" | ||
| # firefox_android: "134" | ||
| # safari: "26" | ||
| # safari_ios: "26" | ||
| - css.properties.align-self.position_absolute_context | ||
| - css.properties.justify-self.position_absolute_context | ||
| - css.properties.place-self.position_absolute_context |
There was a problem hiding this comment.
See #2947, which I need to review and approve. These keys will soon go out of this feature, which is a good thing.
features/clear-site-data.yml.dist
Outdated
|
|
||
| status: | ||
| baseline: low | ||
| baseline: high |
There was a problem hiding this comment.
Agreed. Bug https://issues.chromium.org/issues/364634040 feels serious and should hold the feature back.
| # baseline: false | ||
| # support: | ||
| # safari: "17" | ||
| # safari_ios: "17" | ||
| - css.at-rules.counter-style.symbols |
There was a problem hiding this comment.
Out of scope for this PR, but Safari is the only browser to support images as symbols. Other browsers only support text/ident symbols. It would be great to mint a new feature just for image counter styles. I guess that would require a sub-feature in BCD.
|
|
||
| status: | ||
| baseline: low | ||
| baseline: high |
There was a problem hiding this comment.
Found something a bit surprising in BCD:
safari: [
{
"version_added": "17"
},
{
"prefix": "-webkit-",
"version_added": "17"
}
...
]How come both prefixed and unprefixed versions of this function were added in Safari 17?
Bumps @mdn/browser-compat-data from 7.3.7 to 7.3.8.
Release notes
Sourced from
@mdn/browser-compat-data's releases.Changelog
Sourced from
@mdn/browser-compat-data's changelog.Commits
f78f450Release v7.3.8 (#29267)086d0ccFirefox Nightly adds@container style()behind pref (#29279)6c1d52eOpera Android also supportsContent-Encoding: br(#29265)6be1684Safari 26 supports*-selffor absolutely-positioned boxes (#29299)e967298Firefox 149 adds CSStext-box{,-edge,-trim}behind pref (#29274)a4ea47cChrome 145 addsVideoFrame.metadata()(#29298)c1d17a8letter-spacing: add percentages subfeature (#29200)78781edposition-area: note Chromium bug with absolutely positioned elements (#29283)444e944position-anchor: capture change in initial value (#29272)fcbd3c4position-area: add behavioral subfeature for auto margins (#29280)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 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)