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

CSS :defined - Appears to be discrepancy between Baseline status and support matrix #562

Closed
jacecotton opened this issue Jan 31, 2024 · 4 comments

Comments

@jacecotton
Copy link

jacecotton commented Jan 31, 2024

See here https://developer.mozilla.org/en-US/docs/Web/CSS/:defined

Baseline banner says support is limited with no Firefox or Safari support, but the caniuse data (see table at the bottom of the page) says it's had full support since versions 63 and 10, respectively.

From my reading there doesn't seem to be implementation/spec discrepancies with Firefox or Safari, so not sure why this would show unavailable for them.

@jacecotton
Copy link
Author

Coincidentally I see #561 was just opened by someone else for the JavaScript counterpart to the API. Perhaps it is the differences in implementation for customElementRegistry.define, which in turn affect whether :defined will match, that accounts for the discrepancy here.

@tidoust
Copy link
Member

tidoust commented Jan 31, 2024

Thanks for the report! This issue and #561 (also #530), are occurrences of the problem described in #495: the banner that MDN currently displays on an individual feature page is that of the group this feature is part of, even though the banner is not explicit about that, which is confusing for readers. We're working on a fix with MDN.

In this case, :defined is part of custom-elements, which contains other features that are not yet widely available. In other words, the data itself is correct. It does not claim that :defined has limited availability.

I had closed #530 as covered by #495, but it's perhaps more useful to keep these issues open so that people bump into them when they consider reporting similar problems.

@jacecotton
Copy link
Author

That makes sense! It would definitely be helpful seeing additional text basically saying "X is part of a broader feature set Y which does not have full support in some of the most widely-used browsers" or something along those lines. Thanks for the response.

@LeoMcA
Copy link
Collaborator

LeoMcA commented Feb 8, 2024

Thanks for reporting this, I've added this page (and all others from the custom elements group) to a blocklist on MDN so for now the Baseline banner won't show until we've settled on a more general fix to this problem.

@LeoMcA LeoMcA closed this as completed Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants