docs: fix wording in browser support description #21165
Open
+1
−1
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.
What
Fixes #21144
This PR clarifies the browser support documentation by changing the focus from
browser release dates to feature availability, which better matches the official
Baseline definition.
Before:
After:
Why
The previous wording "browsers that were released at least 2.5 years ago" is
ambiguous and can be misunderstood as:
This is the opposite of what Baseline Widely Available means. According to the
official Baseline definition:
The new wording:
Alternatives Explored
Checklist
Additional Context
See discussion in #21144 where community members agreed the focus should be on
"features available for at least 2.5 years" rather than browser ages.