Feature Request: Explain "Yes" in compatibility tables

[csbrown]

Use Case

Currently, there are many compatibility tables on the MDN network that simply say "Yes" for compatibility with a particular browser, for example here. Apparently "Yes" means "that a sub-feature is supported... with the additional meaning that it is unknown in which version support was added". However, this information is not documented on the website at all, AFAIK, and the "Yes" is quite confusing. I witnessed first hand as a team of experienced web developers misunderstood the table on the Range page by simply ignoring the "Yes" and focusing on the actual numbers underneath, which are for a sub-sub-feature.

Feature Description

Could we document the meaning of "Yes" in this context somewhere? Preferably near the "Yes"?

For example, when one clicks on a versioned entry, an additional date of release is displayed:

When one clicks on a "Yes" entry, it just says "Yes":

Instead, it could possibly say "Yes: Latest version, Earliest supporting version unknown", or some such thing.

Appendix

Apparently MDN has had a war on "Yes" but seems to have given up on the war, so they are here to stay.

[caugner]

We would be accepting a community PR that replaces

Yes
Full support

with

Yes
Full support (earliest supporting release version unknown)

in this case.

[danielhjacobs]

seems to have given up on the war

For reference, 8 files are left that are affected by this issue, and that will reduce to 0 over time:

1. https://github.com/mdn/browser-compat-data/blob/main/webextensions/api/commands.json - Chrome data, fixed by Update Chromium data for commands Web Extensions interface browser-compat-data#24263
2. https://github.com/mdn/browser-compat-data/blob/main/webextensions/api/cookies.json - Chrome data, fixed by Update Chromium data for cookies Web Extensions interface browser-compat-data#24268
3. https://github.com/mdn/browser-compat-data/blob/main/webextensions/api/management.json - Chrome data, fixed by Update Chromium data for management Web Extensions interface browser-compat-data#24278
4. https://github.com/mdn/browser-compat-data/blob/main/webextensions/api/devtools.json - Chrome data, fixed by Update Chromium data for devtools Web Extensions interface browser-compat-data#24270
5. https://github.com/mdn/browser-compat-data/blob/main/webextensions/manifest/background.json - Chrome data, fixed by Update Chromium data for webextensions.manifest.background.type browser-compat-data#24292
6. https://github.com/mdn/browser-compat-data/blob/main/webextensions/manifest/optional_permissions.json - Chrome data, fixed by Update Chromium data for optional_permissions Web Extensions manifest property browser-compat-data#24093
7. https://github.com/mdn/browser-compat-data/blob/main/webextensions/api/menus.json - Chrome data, fixed by Update Chromium data for menus Web Extensions interface browser-compat-data#24277
8. https://github.com/mdn/browser-compat-data/blob/main/webextensions/manifest/commands.json - Chrome data, fixed by Update Chromium data for commands Web Extensions manifest property browser-compat-data#24293

[queengooborg]

Apparently MDN has had mdn/browser-compat-data#3555 but seems to have given up on the war, so they are here to stay.

It's not that the "war" on nonreal values has been abandoned, it's just that at the time, other projects had taken priority. An Open Web Docs project has been commenced to work on removing the nonreal values once again, see openwebdocs/project#206! (And we're almost done as well!)