Skip to content

Commit fda811b

Browse files
authored
Improve README browser version display guidance (#2928)
Fixes #2498
1 parent e9f70e1 commit fda811b

File tree

1 file changed

+4
-1
lines changed

1 file changed

+4
-1
lines changed

packages/web-features/README.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,10 @@ For Baseline iconography, follow this procedure for each feature:
4545

4646
For browser support iconography (that is, browser logos and checkmarks and Xs), follow this procedure for each browser:
4747

48-
1. **Do not** show a version number, whether one is provided.
4948
1. If `status.baseline` is `"high"` or `"low"`, then show a green checkmark (✅, "supported") beside each browser's logo icon.
5049
1. If `status.baseline` is `false` and the browser's `status.support` key (for example, `status.support.edge`) is `undefined` or `false`, then show a gray X ("unsupported") beside the browser's logo icon.
5150
1. If `status.baseline` is `"high"` or `"low"` and the browser's `status.support` key is a string, then show a green checkmark ("supported") beside the browser's logo icon.
51+
52+
If you wish to report browser version numbers, avoid showing version numbers alone.
53+
Developers and users often do not know whether a version number refers to a very recent or old release.
54+
If you must show a version number, consider contextualizing that number by showing a release date, a relative date (such as "Released … years ago"), an offset (such as "… releases ago"), or usage statistics relevant to your audience (such as "…% of your visitors in the last 90 days").

0 commit comments

Comments
 (0)