Clarify downstream browser support on gh-pages site #3245
Conversation
github-actions
bot
added
the
documentation
| > **NOTE** | ||
| > Baseline support for the browsers marked with an asterisk (*) is based on mapping their version number and stated Chromium version from user agent strings captured by [useragents.io](https://useragents.io). This information is provided on a best-effort basis. For more information on how these mappings are generated, please see [the `baseline-browser-mapping` README](https://github.com/web-platform-dx/baseline-browser-mapping/blob/main/README.md#downstream-browsers). | ||
|
|
||
| KaiOS - a feature phone operating system used for flip phones - implements the Gecko engine from Firefox. It is possible to derive feature support in KaiOS based on Gecko feature support, but please be aware that KaiOS has a significantly different set of UI limitations and interaction model compared to the other browsers on this page. For more information, see the [KaiOS developer documentation](https://developer.kaiostech.com/docs/sfp-3.0/). |
There was a problem hiding this comment.
I'm honestly on the fence about mentioning KaiOS in here, but we are adding support behind a special config option in bbm, so it probably makes sense to have something.
| @@ -27,6 +27,28 @@ You can find at-a-glance Baseline statuses on [Can I Use](https://caniuse.com/) | |||
|
|
|||
| You can [use Baseline on your site](/use-baseline/) too. | |||
|
|
|||
| ## What about other browsers? | |||
There was a problem hiding this comment.
I'd suggest moving this section up by one (above "How do I find...") so it's closer to the list of core browsers.
Should we also link to https://web-platform-dx.github.io/web-features/supported-browsers/?includeDownstream=true somewhere in here?
There was a problem hiding this comment.
I'd suggest moving this section up by one (above "How do I find...") so it's closer to the list of core browsers.
This was my original though as well, but the section is quite long and I didn't want to bury the "find a feature", thing. @ddbeck, do you have a strong view here? I agree that it makes sense closer to the list of core browsers.
Should we also link to https://web-platform-dx.github.io/web-features/supported-browsers/?includeDownstream=true somewhere in here?
At some point I had a para that linked to this but I must have deleted. Will find somewhere for it to go 👍
There was a problem hiding this comment.
I think I'd be OK with moving the section to immediately follow the browser list, though I have another (more dramatic) suggestion below that might make it easier to do that without pushing the next question off screen as often.
| Most modern browsers are built on the rendering engine from one of the browsers in the Baseline core browser set. | ||
|
|
||
| All browsers on iOS currently implement WebKit, the Safari rendering engine. | ||
|
|
||
| The majority of browsers outside the core browser set on Android, Windows and macOS are built on Chromium/Blink, the open source engine underpinning Chrome and Edge. These browsers can usually be mapped back to the Baseline feature set they support based on the Chromium version they implement. The [`baseline-browser-mapping`](https://github.com/web-platform-dx/baseline-browser-mapping) module tracks these mappings, and currently includes data on the following browsers: | ||
|
|
||
| - Opera Desktop and Mobile | ||
| - Samsung Internet | ||
| - Android WebView | ||
| - QQ Browser Mobile\* | ||
| - UC Browser Mobile\* | ||
| - Yandex Browser Mobile\* | ||
|
|
||
| See [supported browsers](/supported-browsers/?includeDownstream=true) to find out which minimum browser versions support different Baseline feature sets, includeing Newly and Widely available and Baseline years. | ||
|
|
||
| > **NOTE** | ||
| > Baseline support for the browsers marked with an asterisk (\*) is based on mapping their version number and stated Chromium version from user agent strings captured by [useragents.io](https://useragents.io). This information is provided on a best-effort basis. For more information on how these mappings are generated, please see [the `baseline-browser-mapping` README](https://github.com/web-platform-dx/baseline-browser-mapping/blob/main/README.md#downstream-browsers). |
There was a problem hiding this comment.
I have a suggestion for this whole section, but it's a bit radical: what if we elide a lot of detail and then use the supported browsers page to list out the browser names?
Many browsers outside the core browser set typically support the same Baseline feature set as a browser in the core browser set.
For example, many browsers on Android, Windows, and macOS are built on Chromium, the open source engine underpinning Chrome and Edge. On iOS, all browsers use the same engine, WebKit, that underpins that device's Safari browser.
For a wider range of browsers, see [supported browsers](/supported-browsers/?includeDownstream=true) to find out which minimum browser versions support different Baseline feature sets, including Newly and Widely available and Baseline years.
The [`baseline-browser-mapping`](https://github.com/web-platform-dx/baseline-browser-mapping) module tracks these mappings to derive the feature set for browsers outside the core browser set.
There was a problem hiding this comment.
I don't know why my suggestion is broken. Maybe this is easier to read:
Many browsers outside the core browser set typically support the same Baseline feature set as a browser in the core browser set.
For example, many browsers on Android, Windows, and macOS are built on Chromium, the open source engine underpinning Chrome and Edge. On iOS, all browsers use the same engine, WebKit, that underpins that device's Safari browser.
For a wider range of browsers, see supported browsers to find out which minimum browser versions support different Baseline feature sets, including Newly and Widely available and Baseline years.
The
baseline-browser-mappingmodule tracks these mappings to derive the feature set for browsers outside the core browser set.
| @@ -27,6 +27,28 @@ You can find at-a-glance Baseline statuses on [Can I Use](https://caniuse.com/) | |||
|
|
|||
| You can [use Baseline on your site](/use-baseline/) too. | |||
|
|
|||
| ## What about other browsers? | |||
There was a problem hiding this comment.
I think I'd be OK with moving the section to immediately follow the browser list, though I have another (more dramatic) suggestion below that might make it easier to do that without pushing the next question off screen as often.
|
|
||
| KaiOS - a feature phone operating system used for flip phones - implements the Gecko engine from Firefox. It is possible to derive feature support in KaiOS based on Gecko feature support, but please be aware that KaiOS has a significantly different set of UI limitations and interaction model compared to the other browsers on this page. For more information, see the [KaiOS developer documentation](https://developer.kaiostech.com/docs/sfp-3.0/). | ||
|
|
||
| Other browsers built on Chromium/Blink, Gecko and WebKit will also support Baseline features, and the WebDX Community Group is continuing to work on mapping downstream browser versions back to the engine they implement. If you work on a browser and can provide data connecting your versions back to their upstream engine for `baseline-browser-mapping`, please [create an issue in the repository](https://github.com/web-platform-dx/baseline-browser-mapping/issues/new). |
There was a problem hiding this comment.
This could go on the supported browsers page, after the list, with something like:
Don't see a browser you're expecting? If you work on a browser and can provide data connecting your versions back to their upstream engine for
baseline-browser-mapping, please create an issue in the repository.
As discussed in this week's WebDX CG meeting, this draft adds a section in the main Baseline definition page that describes the relationship between Baseline and browsers outside the core set.
CC: @ddbeck @ai @rviscomi