Skip to content
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

Should features not ready for implementation be tested? #243

Open
SebastianZ opened this issue Mar 26, 2023 · 0 comments
Open

Should features not ready for implementation be tested? #243

SebastianZ opened this issue Mar 26, 2023 · 0 comments
Labels

Comments

@SebastianZ
Copy link
Collaborator

There are several specifications that are marked as "Not ready for implementation" like CSS Color 6 or CSS Backgrounds 4. And there are also individual features within different specs that are marked as at-risk like e.g. font-language-override in CSS Fonts 4, the scroll value of spatial-navigation-action in CSS Spatial Navigation 1 or the :blank pseudo-class of Selectors 4.

Currently, we have mixed coverage of those features and specs. Should we cover all of them, should we remove them, or should we mark them as "highly experimental" somehow?

I'd initially remove them if there are no implementations yet. In a second step I'd add them back with a hint that they are highly experimental and exclude them from the score. And maybe a new filter could be added to cover them.

Sebastian

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

No branches or pull requests

1 participant