web-features 2.34.2 → 2.35.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +4 -1
- package/data.json +1 -1
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -45,7 +45,10 @@ For Baseline iconography, follow this procedure for each feature:
|
|
|
45
45
|
|
|
46
46
|
For browser support iconography (that is, browser logos and checkmarks and Xs), follow this procedure for each browser:
|
|
47
47
|
|
|
48
|
-
1. **Do not** show a version number, whether one is provided.
|
|
49
48
|
1. If `status.baseline` is `"high"` or `"low"`, then show a green checkmark (✅, "supported") beside each browser's logo icon.
|
|
50
49
|
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.
|
|
51
50
|
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").
|