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

> For APIs who don't internally call into algorithms that operate on scalar values, but instead just operate on un-interpreted strings, you would never write that preprocessing step, with all of its associated costs. So such APIs should just use DOMStrings, and not add the additional preprocessing that USVStrings bring along.

This isn't completely true. In at least Servo's architecture, USVStrings are the cheaper data structure to support (if i'm recalling correctly), which is the whole reason we added CSSOMString - so impls could choose one or the other to use consistently thru CSS.

(I don't have a horse in this race otherwise, I just want a clear answer.)

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

Received on Thursday, 22 February 2018 19:27:28 UTC