An interesting data point: Firefox still crashes when inspecting the 
property for a styleSheet in this state (test 
<https://wholesale-accidental-trunk.glitch.me/>). I guess that's good 
motivation on their end to make this update and remain interoperable.

-- Dan

On Friday, February 23, 2024 at 5:32:37 AM UTC-8 amo...@gmail.com wrote:

> Contact emailseui-sa...@samsung.com
>
> ExplainerNone
>
> Specificationhttps://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 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
>
> *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
>  
>
>
> Flag name on chrome://flags
>
> Finch feature nameCSSImportRuleStyleSheetNullable
>
> Requires code in //chrome?False
>
> Tracking bughttps://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/d06d20b5-ec87-47b3-83cf-4c79081884e8n%40chromium.org.

Reply via email to