We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Incorrect support data (example: BrowserX says "86" but support was added in "40")
The footnote “3 The root element cannot be a container” should also apply to Safari 18.1 TP.
Safari
It should match the data from https://caniuse.com/mdn-css_at-rules_container_style_queries_for_custom_properties (footnote 1). Footnote 3 from the incorrect page should also apply to Safari 18.1 TP and not just Safari 18.0
I did not test this.
I’m mostly sure that the first page is wrong, but it’s possible I misinterpreted the data and it’s actually the second page.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What type of issue is this?
Incorrect support data (example: BrowserX says "86" but support was added in "40")
What information was incorrect, unhelpful, or incomplete?
The footnote “3 The root element cannot be a container” should also apply to Safari 18.1 TP.
What browsers does this problem apply to, if applicable?
Safari
What did you expect to see?
It should match the data from https://caniuse.com/mdn-css_at-rules_container_style_queries_for_custom_properties (footnote 1). Footnote 3 from the incorrect page should also apply to Safari 18.1 TP and not just Safari 18.0
Did you test this? If so, how?
I did not test this.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
Do you have anything more you want to share?
I’m mostly sure that the first page is wrong, but it’s possible I misinterpreted the data and it’s actually the second page.
MDN URL
No response
MDN metadata
No response
The text was updated successfully, but these errors were encountered: