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

Jump to bottom

Handle more complex browser-compat-data #107

Closed

octref opened this issue Jun 18, 2018 · 1 comment

Assignees

Labels

feature-request

Milestone

Contributor

octref commented Jun 18, 2018

Continuation of #105

There are a few cases in the data that we don't handle.

Support was added under an experimental flag

For those that have become standardized, we can just display the latest supported version. (e.g., supported through flag in ver 1, become officially supported in v2, we can just show Browser V2)
For those that haven't become standardized. We need to find a way to display the information. For example Chrome 61 with flag. @aeschli What do you think?

Support is not chronological, for example: Linter: Make sure multiple version ranges are sorted according to some rules mdn/browser-compat-data#1596. We can worry about this later, as mdn/browser-compat-data seem to have plan for enforcing certain linting rules on the order of support data.

The text was updated successfully, but these errors were encountered:

octref self-assigned this

octref added the feature-request label

octref mentioned this issue

Import mdn/browser-compat-data. Fix #102 #105

Merged

aeschli added this to the Backlog milestone

aeschli assigned aeschli and unassigned octref

Contributor

aeschli commented Nov 11, 2020

Closing, no plans for now

aeschli closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment