Skip to content

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.

Sign up for GitHub

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

Open
captainbrosset wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Some clarification about what Baseline is and isn't #3626

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# [`web-features`](https://github.com/web-platform-dx/web-features): exploring the set of interoperable features of the web platform
Copy link
Collaborator

@dfabulich dfabulich Dec 11, 2025

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

# [`web-features`](https://github.com/web-platform-dx/web-features): exploring the set of features of the web platform

By the [W3C WebDX Community Group](https://www.w3.org/community/webdx/) and contributors.

Expand Down
2 changes: 1 addition & 1 deletion gh-pages/src/_includes/default.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@
</a>

<p>
Baseline gives you clear information about which web platform features work across browsers.
Copy link
Collaborator

@dfabulich dfabulich Dec 11, 2025

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.

Baseline gives you summarized information about which web platform features work across browsers.
</p>

<ul class="nav">
Expand Down
2 changes: 1 addition & 1 deletion gh-pages/src/assets/css/style.css
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ body {
background-color: #fff;
padding: 3.5em;
font:
14px/1.5 "Noto Sans",
14px/1.7 "Noto Sans",
"Helvetica Neue",
Helvetica,
Arial,
Expand Down
25 changes: 20 additions & 5 deletions gh-pages/src/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,16 +3,31 @@ layout: "default.html"
title: "What is Baseline?"
---

Baseline gives you clear information about which web platform features work across our [core browser set](#how-do-features-become-part-of-baseline%3F) today. When reading an article, or choosing a library for your project, if the features used are all part of Baseline, you can trust the level of browser compatibility. By aligning with Baseline, there should be fewer surprises when testing your site.
Baseline gives you summarized information about which web platform features work across our [core browser set](#which-browsers-are-in-the-core-browser-set) today.

When you read an article about features of the web platform, or when you choose a library that uses web features for your project, if those features are all Baseline, you can make quicker decisions about using them. Baseline helps to reduce the number of cross-browser surprises when testing your site.

## How do features become part of Baseline?

Baseline features are available across popular browsers. Baseline has two stages:
Baseline has two stages:

- **Newly available**

The feature has recently become available in all the browsers of the core browser set. The feature might not work yet in older devices or browsers.
This status is indicated with the following blue icon: <img src="/assets/img/baseline-widely-icon.svg" alt="Baseline widely available icon" style="height:1em;">.

- **Widely available**

The feature has been available in all the browsers of the core browser set for at least 2½ years (30 months). It is now well established and works across many devices and browser versions.
This status is indicated with the following green icon: <img src="/assets/img/baseline-newly-icon.svg" alt="Baseline newly available icon" style="height:1em;">.

Prior to being part of Baseline, a feature has **Limited availability** when it's not yet available across all the browsers of the core browser set.
Limited availability features are indicated with the following grey and orange icon: <img src="/assets/img/baseline-limited-icon.svg" alt="Limited availability icon" style="height:1em;">

- **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.
Copy link
Collaborator

@dfabulich dfabulich Dec 11, 2025

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.

For example, a feature that's limited availability or Baseline newly available might still work well enough for your needs, or as a progressive enhancement. Or, a feature that's Baseline widely available might not work for your specific audience if they use older browsers or devices.

Prior to being newly available, a feature has **Limited availability** when it's not yet available across all browsers.
## Which browsers are in the core browser set?

Baseline is calculated using the following core browser set:

Expand Down
Loading