One open issue that I didn't see mentioned and is worth noting, is a
missing equivalent in <link> elements (similar to <link media=...>. This
creates an inconsistency where you can have conditional imports in CSS but
not directly from HTML. This is mentioned in
https://github.com/whatwg/html/issues/7540. Not saying it should block
shipping, but rather that it should be considered an open issue.

On Wed, Nov 22, 2023 at 5:47 AM Yoav Weiss <yoavwe...@chromium.org> wrote:

> LGTM1
>
> While I'm not excited about @import in general and think no one should use
> it, this restricts it in potentially useful ways.
>
> On Wednesday, November 15, 2023 at 3:28:48 PM UTC+1 Daniil Sakhapov wrote:
>
>> Contact emailssakha...@chromium.org
>>
>> Specificationhttps://www.w3.org/TR/css-cascade-5/#conditional-import
>>
>> Summary
>>
>> It allows to import stylesheets and layers conditioned on supports(). If
>> the support() doesn't match, the import will not be fetched.
>>
>>
>> Example: @import "mystyle.css" supports(display: flex);
>>
>> Blink componentBlink>CSS
>> <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS>
>>
>> TAG reviewNone
>>
>> TAG review statusNot applicable
>>
>> Risks
>>
>>
>> Interoperability and Compatibility
>>
>> None
>>
>>
>> *Gecko*: Shipped/Shipping
>>
>> *WebKit*: No signal (
>> https://github.com/WebKit/standards-positions/issues/279)
>>
>> *Web developers*: No signals
>>
>> *Other signals*:
>>
>> WebView application risks
>>
>> Does this intent deprecate or change behavior of existing APIs, such that
>> it has potentially high risk for Android WebView-based applications?
>>
>> None
>>
>> Will this feature be supported on all six Blink platforms (Windows, Mac,
>> Linux, Chrome OS, Android, and Android WebView)?Yes
>>
>> Is this feature fully tested by web-platform-tests
>> <https://chromium.googlesource.com/chromium/src/+/main/docs/testing/web_platform_tests.md>
>> ?Yes
>>
>> https://wpt.fyi/results/css/css-cascade/import-conditions.html
>> https://wpt.fyi/css/cssom/cssimportrule.html
>>
>>
>> Flag name on chrome://flagsCSSSupportsForImportRules
>>
>> Requires code in //chrome?False
>>
>> Estimated milestones
>> DevTrial on desktop 121
>> DevTrial on Android 121
>>
>> Anticipated spec changes
>>
>> Open questions about a feature may be a source of future web compat or
>> interop issues. Please list open issues (e.g. links to known github issues
>> in the project for the feature specification) whose resolution may
>> introduce web compat/interop risk (e.g., changing to naming or structure of
>> the API in a non-backward-compatible way).
>> None
>>
>> Link to entry on the Chrome Platform Status
>> https://chromestatus.com/feature/5899007704694784
>>
>> This intent message was generated by Chrome Platform Status
>> <https://chromestatus.com/>.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "blink-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to blink-dev+unsubscr...@chromium.org.
> To view this discussion on the web visit
> https://groups.google.com/a/chromium.org/d/msgid/blink-dev/13305766-65c8-427c-85a4-fc457c855bf0n%40chromium.org
> <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/13305766-65c8-427c-85a4-fc457c855bf0n%40chromium.org?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"blink-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to blink-dev+unsubscr...@chromium.org.
To view this discussion on the web visit 
https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAJn%3DMYYsLu_ndEd75PdsAeRZ%3DffHNb7zTufM_1mZRyHYRgTphw%40mail.gmail.com.

Reply via email to