Update v5 .browserslistrc #41390
Description
v5 has been around for almost five years (with the first alpha release in June 2020). In that time, browser support for new CSS and JS features has really accelerated, and Bootstrap 5 hasn't progressed to support that.
I'd like to modify the supported browsers in v5.4 to push the project forward to more modern features.
Here's our list today with 96% coverage:
>= 0.5%
last 2 major versions
not dead
Chrome >= 60
Firefox >= 60
Firefox ESR
iOS >= 12
Safari >= 12
not Explorer <= 11
not kaios <= 2.5
Bumping some of these drops us to 94.4%:
>= 0.5%
last 2 major versions
not dead
**Chrome >= 105
**Firefox >= 121
Firefox ESR
**iOS >= 15.4
**Safari >= 15.4
not Explorer <= 11
not kaios <= 2.5
I targeted those versions to at least get :has(), but we may even want to further refine them and see what features we want access to without making folks upgrade to v6.
This in theory also goes well with the Sass modules support which will be a breaking change within v5.
More to come but I wanted to get this out there before I forgot and collect some initial thoughts.
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
Participants
Activity
julien-deramond commentedon Apr 17, 2025
To connect existing elements, the description in #37309 includes references related to a potential update of the
.browserslistrcfile.mdo commentedon Apr 18, 2025
Was looking at some compatibility tables and trying to find what features we'd want to see about adding support for in v5.x. Not exhaustive, but there are a handful if we jump to Safari 15.4-ish and Chrome 100-ish.
@containerand container@layer@propertyjulien-deramond commentedon Apr 18, 2025
The goal was to get a general sense of the ecological impact of supporting Safari 15 and above.
I started looking into this out of curiosity, since I never use Safari myself. But I’ve seen use cases where websites rendered poorly on otherwise perfectly functional Macs less than 10 years old, simply because the sites relied on features only available in more recent browser versions. That made me wonder how non-technical users might be impacted.
To make matters trickier, Safari versions are tied to macOS versions — and macOS updates are often locked out on older Macs. So even if the hardware is capable, users might be stuck with an outdated Safari.
Some features may still work thanks to fallbacks, so a proper assessment would require a feature-by-feature analysis.
Based on this early overview — if the findings hold up — Safari 15.4-ish might be a reasonable baseline to aim for.
Warning
This overview was generated by AI to give a general sense of the results — I haven’t manually verified it yet.
Apple Devices Stuck Below Safari 15
These devices are found by AI incompatible with Safari 15 or higher, due to OS limitations. By updating our
.browserslistrctoSafari >= 15, these users would no longer be supported.iPhones
iPads
Macs
* Only supports Mojave if upgraded with a compatible GPU.
Safari 15+ Support Starts With:
louismaximepiton commentedon Apr 24, 2025
On our project, we might define the same baseline as the ones in here. We had several discussions about it internally, but we've decided almost the same as yours:
My main concerns go for:
Here is our findings about our
.browserlistrc: Orange-OpenSource/Orange-Boosted-Bootstrap#2929mdo commentedon Apr 24, 2025
@louismaximepiton Wow amazing PR there with the supported features. Appreciate that! I think we'll end up going that route as well after reviewing your PR another time.
coliff commentedon Apr 25, 2025
All looks good to me- happy to see the browser support updated!
One minor thing,
not Explorer <= 11can be completely removed from the config - it's not necessary to state that because a) it's browser marketshare is less than 0.5% so it wouldn't be included anyway, and b) it's also excluded as part of thenot deadrule.