-
Notifications
You must be signed in to change notification settings - Fork 224
Some clarification about what Baseline is and isn't #3626
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
| @@ -1,4 +1,4 @@ | |||
| # [`web-features`](https://github.com/web-platform-dx/web-features): exploring the set of interoperable features of the web platform | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest:
defining the list of features of the web platform and determining their Baseline status
| </a> | ||
|
|
||
| <p> | ||
| Baseline gives you clear information about which web platform features work across browsers. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Throughout, this PR replaces "clear" with "summarized." I don't love that.
IMO, the main problem we're referring to in #2783 isn't that people don't realize that Baseline is a summary; it's a false-negative problem. If something is Baseline WA, you can use it, but people might wrongly assume that if something is NA or LA, then you simply can't use it, and you'll just have to wait.
If we all agreed that Baseline wasn't "clear," then I think Baseline wouldn't be useful at all, but I think it is useful because it is clear.
|
|
||
| - **Newly available**: The feature works across the latest devices and browser versions. The feature might not work in older devices or browsers. Indicated with a blue icon. | ||
| - **Widely available**: The feature is well established and works across many devices and browser versions. It’s been available across browsers for at least 2½ years (30 months). Indicated with a green icon. | ||
| Baseline is a simplification of the complex reality of web platform feature support, and it can't replace detailed testing for your specific use case. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is too strong a disclaimer,. This makes it sound like Baseline should never replace detailed testing. (And it makes it sound like we encourage all developers to do the tests themselves, rather than rely on BCD.)
I suggest:
Features that aren't yet available in all browsers might still work well enough for your needs, as a progressive enhancement with a fallback, or by using a polyfill or transpiler.
This is a partial fix to #2783, in particular to this point:
Although this is not a change of the Baseline definition, I feel like the owners group should review this.