Re: [csswg-drafts] [cssom] should custom properties be exposed on computed style declarations? (#1316)

The CSS Working Group just discussed `should custom properties be exposed on computed style declarations?`, and agreed to the following:

* `RESOLVED: non-initial custom properties should be exposed on computed style objects, open a new issue about defining order`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: should custom properties be exposed on computed style declarations?<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1316<br>
&lt;dael> Rossen_: heycam added and then lively discussion. Who wants this?<br>
&lt;dael> TabAtkins: I can. I support it. If we allow interaction of custom prop via OM we should expose what's non-initial. Makes sense to make when you gCS from there. Technical questions on the API, but can be resolved by emilio as he feels fit.<br>
&lt;dael> TabAtkins: Should resolve non-initial custom prop should be exposed on computed style objects<br>
&lt;dael> Rossen_: Other opinions?<br>
&lt;emilio> There's an issue with ordering of properties<br>
&lt;dael> Rossen_: Objections to non-initial custom properties should be exposed on computed style objects<br>
&lt;emilio> Also, what happens with registered properties that have an initial value<br>
&lt;dael> Rossen_: emilio points out issue with ordering?<br>
&lt;dael> Rossen_: Does that change opinion?<br>
&lt;emilio> Basically, order in WebKit is just hash ordering, Gecko is cascade order. Defining alphabetic ordering or such may be problematic (need to sort every indexed operation and such)<br>
&lt;emilio> Leaving ordering undefined might be ok<br>
&lt;dael> TabAtkins: I think it's still useful. Need to figure out the answer. I'm confident emilio will put something good in the spec. What's the order you all use?<br>
&lt;dael> Rossen_: Gecko says cascade<br>
&lt;dael> Rossen_: Order undefined would be a lot of contridictory behavior<br>
&lt;dael> Rossen_: Resolve on adding and open issue on dealing with order?<br>
&lt;dael> TabAtkins: Okay<br>
&lt;emilio> Sgtm<br>
&lt;dael> Rossen_: Support overall behavior. Technical order issue should be sep.<br>
&lt;dael> Rossen_: Prop: non-initial custom prop should be exposed on computed style objects, open a new issue about defining order<br>
&lt;dael> RESOLVED: non-initial custom properties should be exposed on computed style objects, open a new issue about defining order<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1316#issuecomment-486332571 using your GitHub account

Received on Wednesday, 24 April 2019 16:58:15 UTC