-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Update @import … supports()
support
#22164
Conversation
this is dumplite with #22163 |
Let's merge this one instead of mine, it better documents why it doesn't (yet) work in Chrome 121. What are the odds that we both opened a change for this, so close together :D |
This PR relies on #22165 getting merged in first though, as it refers to the Chromium Issue Tracker using the new URL format. (@ reviewer: To unblock this PR, I can change the
I tend to subscribe to the (to me) relevant bugs :) – Thanks for leaving your original reply, as we got it wrong there indeed. |
As there is some ongoing discussion in #22165 I have updated the URL to the crbug.com format. That way, this PR can be approved/merged separately. |
Webkit also implemented this and it is available in the latest Technology Preview : WebKit/WebKit@8338db4 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your PR! LGTM as is. Do you want to set safari to "preview"?
Done. |
Even better, thank you! 👍 |
👋 Hi, Chrome DevRel here
@import … supports()
shipped in Chrome 122.Links:
Note that ChromeStatus mentions it shipping in 121 but that’s not the case. The flag only got flipped in commit
6ca8ac7e347b73c62609643164a444719f9d26f7
, which is only included in M122. See https://chromiumdash.appspot.com/commit/6ca8ac7e347b73c62609643164a444719f9d26f7 for details.