Re: [css-houdini-drafts] Should we be using DOMString, USVString, or CSSOMString?

The Working Group just discussed `schedule wrangling`, and agreed to the following resolutions:

* `RESOLVED: specify USVString for all new Houdini APIs?`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: schedule wrangling<br>
&lt;dael> smfr: We probably need AmeliaBR for the Opacity item.<br>
&lt;AmeliaBR> I can call in... just a sec<br>
&lt;dael> astearns: We can do Houdini and then do this?<br>
&lt;dael> smfr: Fine<br>
&lt;astearns> Should we be using DOMString, USVString, or CSSOMString? - https://github.com/w3c/css-houdini-drafts/issues/687<br>
&lt;dael> github: https://github.com/w3c/css-houdini-drafts/issues/687<br>
&lt;dael> TabAtkins: Should things be spec as DOMString, USVString, or CSSOMString. I need guidance. I got that URL should be USV, but for the rest I'm not sure what to do. ANy guidance appriciated.<br>
&lt;dael> plinss: In general I think we should be doing USV and only DOM where we need it for backwards compat<br>
&lt;dael> TabAtkins: And we did CSSOM to allow that but for engines that are more efficient on DOM to do that.<br>
&lt;dael> plinss: That's why I'm thinking for new APIs let's do USV and not propigate more DOM<br>
&lt;dael> florian: Reason for CSSOM was an impl difficulty I thought<br>
&lt;dael> gsnedders: But elsewhere in platform spec have changed dom to usv. I'm not sure why we have cssom at all rather then we expect will change.<br>
&lt;dael> florian: cssom is for should do usv but do dom if you have to<br>
&lt;dael> plinss: Reality is they will do that so why give them permission to do it wrong if they can do it right?<br>
&lt;dael> astearns: Sound to me like general consensus is to use usv. I'm not hearing anyone cheer for cssom.<br>
&lt;dael> florian: Then we should move away from cssom everywhere.<br>
&lt;dael> astearns: Fair but we can try it with this new API and any in the future and see how much we can go back as we find out if this one works.<br>
&lt;dael> astearns: Objections to spec USVString for this Houdini API?<br>
&lt;dael> TabAtkins: might as well be all<br>
&lt;dael> astearns: Objections to spec USVString for all new Houdini APIs?<br>
&lt;dael> RESOLVED: specify USVString for all new Houdini APIs?<br>
</details>


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

Received on Wednesday, 21 February 2018 17:46:09 UTC