On 2/23/24 8:31 AM, Amos Lim wrote:


        Contact emails

eui-sang....@samsung.com


        Explainer

None
Would you mind explaining why this is a useful addition for developers? Or is the motivation improved spec compliance?


        Specification

https://drafts.csswg.org/cssom/#the-cssimportrule-interface


        Summary

Allow CSSImportRule.styleSheet to be nullable. The styleSheet attribute in CSSImportRule can be null if there is no associated CSS style sheet.



        Blink component

Blink>CSS <https://bugs.chromium.org/p/chromium/issues/list?q=component:Blink%3ECSS>


        TAG review

None


        TAG review status

Not applicable


        Risks



        Interoperability and Compatibility

None



/Gecko/: Shipped/Shipping

/WebKit/: No signal
Can you request a signal? https://github.com/WebKit/standards-positions

/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



        Debuggability

None



        Will this feature be supported on all six Blink platforms
        (Windows, Mac, Linux, ChromeOS, Android, and Android WebView)?

No


        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/cssom/cssimportrule.html?label=experimental&label=master&aligned <https://wpt.fyi/results/css/cssom/cssimportrule.html?label=experimental&label=master&aligned>

All of these tests are passing right now - will you be adding new tests?


        Flag name on chrome://flags



        Finch feature name

CSSImportRuleStyleSheetNullable


        Requires code in //chrome?

False


        Tracking bug

https://issues.chromium.org/issues/40266154


        Estimated milestones

Shipping on desktop     124

Shipping on Android     124

Shipping on WebView     124



        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/5123480866783232

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/CAOGEg03EdbMR2-x-7taf692_FmX4%2BwBMgFW%2BwaZiM7gs1Zo5-Q%40mail.gmail.com <https://groups.google.com/a/chromium.org/d/msgid/blink-dev/CAOGEg03EdbMR2-x-7taf692_FmX4%2BwBMgFW%2BwaZiM7gs1Zo5-Q%40mail.gmail.com?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/032d8d45-c28b-439d-a72c-fff1f0b535e8%40chromium.org.

Reply via email to