Re: [csswg-drafts] [cssom] How safe is it really to shorthandify properties? (#8398)

> I initially thought css-typed-om might be a problem, since there is no shorthand support there. (But then I found that the spec seems to allow it, it's just Blink's incomplete implementation that doesn't support it).

@kojiishi points out that this _is_ actually a (spec) problem too:

https://drafts.css-houdini.org/css-typed-om/#computed-stylepropertymapreadonly-objects: 

> If this’s [[[computedStyleMapCache]]](https://drafts.css-houdini.org/css-typed-om/#dom-element-computedstylemapcache-slot) internal slot is set to null, set its value to a new [StylePropertyMapReadOnly](https://drafts.css-houdini.org/css-typed-om/#stylepropertymapreadonly) object, whose [[[declarations]]](https://drafts.css-houdini.org/css-typed-om/#dom-stylepropertymapreadonly-declarations-slot) internal slot are the name and [computed value](https://drafts.csswg.org/css-cascade-5/#computed-value) of every **longhand** CSS property supported by the User Agent, every registered [custom property](https://drafts.csswg.org/css-variables-2/#custom-property), and every non-registered [custom property](https://drafts.csswg.org/css-variables-2/#custom-property) which is not set to its initial value on this, in the standard order.


-- 
GitHub Notification of comment by andruud
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8398#issuecomment-1608794475 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 27 June 2023 04:52:51 UTC