Skip to content
This repository has been archived by the owner on Jul 21, 2021. It is now read-only.

Use MDN's browser-compat-data for browser status info #534

Open
connorshea opened this issue Jul 30, 2018 · 2 comments
Open

Use MDN's browser-compat-data for browser status info #534

connorshea opened this issue Jul 30, 2018 · 2 comments

Comments

@connorshea
Copy link

The MDN browser-compat-data project is at a point now where almost all of MDN's compatibility tables have been moved over to it.

I think it'd be a good idea to change the Platform Status site such that the data for support in browsers other than Firefox is sourced from the BCD package.

Using the BCD package would do a few things:

  • The Platform Status site would have more accurate, up-to-date data on external browser support
  • This would help to centralize the data in a single place for multiple browser vendors to contribute
  • The data could be more granular, e.g. including the specific browser version a given feature was implemented in, or whether the browser implements all of the subfeatures for a given API.

For one example of data that would be significantly improved, right now the Abort API has no info for any browser other than Firefox, but the MDN article's compatibility table, powered by the browser-compat-data package, has detailed info on every major browser.

On the Platform Status site:
screen shot 2018-07-30 at 5 50 09 pm

On the MDN article:
screen shot 2018-07-30 at 5 50 14 pm

@connorshea connorshea changed the title Use MDN's browser-compat-data to power the site Use MDN's browser-compat-data for browser status info Jul 30, 2018
@stof
Copy link
Contributor

stof commented Aug 2, 2018

Getting data only from BCD might not work, as it won't have the distinction between "no signals", "considering" or "in development" (as far as BCD is concerned, all these are "no support"). But it might indeed be good as an input, to at least mark any supported feature as shipped.

@connorshea
Copy link
Author

Yup, that was what I was thinking. Its not very useful for signaling necessarily but it is useful for features that have been implemented.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants