You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
These browsers account for 95.92% of all users globally
:focus-visible
We already began to use :focus-visible but haven't updated yet our .browserslistrc. Let's check what is the impact and if we can consider that we live with this mismatch we have now and fix it for the next v5.3.0.
⚠️ Temporary added 60ff612 in this PR in order to do some BrowserStack testing.
It seems like it was really well supported since last year (15.4) only.
Your CanIUse link shows that backface-visibility has been supported with the -webkit- prefix since 2013, though? Bootstrap uses AutoPrefixer, so the prefixed version is automatically added into the built CSS. You can see that in action here for .carousel-item.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description / Motivation & Context
Based on #37306, I'm starting a PR to update our list of supported browsers contained in
.browserslistrc.Actual support
npx autoprefixer --info
npx autoprefixer --info (0.000679 hrs) Browsers: Chrome for Android: 106 Firefox for Android: 105 QQ Browser: 13.1 UC for Android: 13.4 Android: 106 Chrome: 106, 105, 104, 103, 102, 101, 100, 99, 98, 97, 96, 95, 94, 93, 92, 91, 90, 89, 88, 87, 86, 85, 84, 83, 81, 80, 79, 78, 77, 76, 75, 74, 73, 72, 71, 70, 69, 68, 67, 66, 65, 64, 63, 62, 61, 60 Edge: 106, 105, 104 Firefox: 105, 104, 103, 102, 101, 100, 99, 98, 97, 96, 95, 94, 93, 92, 91, 90, 89, 88, 87, 86, 85, 84, 83, 82, 81, 80, 79, 78, 77, 76, 75, 74, 73, 72, 71, 70, 69, 68, 67, 66, 65, 64, 63, 62, 61, 60 iOS Safari: 16.0, 15.6, 15.5, 15.4, 15.2-15.3, 15.0-15.1, 14.5-14.8, 14.0-14.4, 13.4-13.7, 13.3, 13.2, 13.0-13.1, 12.2-12.5, 12.0-12.1 KaiOS Browser: 2.5 Opera Mini: all Opera Mobile: 64 Opera: 91, 90 Safari: 16.0, 15.6, 15.5, 15.4, 15.2-15.3, 15.1, 15, 14.1, 14, 13.1, 13, 12.1, 12 Samsung Internet: 18.0, 17.0These browsers account for 95.92% of all users globally
:focus-visibleWe already began to use
:focus-visiblebut haven't updated yet our.browserslistrc. Let's check what is the impact and if we can consider that we live with this mismatch we have now and fix it for the next v5.3.0.See also https://github.com/orgs/twbs/discussions/37306
TODO: check what values would need to be changed and what is the impact
TODO: change values in
.browserslistrcprefers-color-schemeWill be used in the dark mode.
TODO: add more details
TODO: explain what values need to be changed
TODO: change values in
.browserslistrcxlink:href→hrefSee #39222
Breaking changes too important for now
bootstrap/scss/_nav.scss
Line 147 in 42e99cc
Others
:hasselector):hasselector +:focus-visible)gapof.nav-underlineType of changes
Checklist
npx update-browserslist-db@latestto update ourpackage-lock.json