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

My understanding of Servo is that it _can_ support DOMStrings (using wtf-8), but it also has support for utf-8 based USVStrings without requiring additional processing. I believe Tab's point is that USVStrings are cheaper in Servo, not required, so this is not based on a limitation, but rather a desire to "do it right" in the API (for some value of right).

So if the argument is to use DOMStrings because they cheaper to implement, we have existence proof to the contrary.

Like Tab, I don't have a horse in this race, and I also just want a clear answer. If this was previously litigated, I have no desire to re-litigate, but I also want to know that the answer was based on solid principles and good information.

I also don't want CSS to be inconsistent with the rest of the platform, but I do want the platform to be able to evolve and not be constrained by legacy implementations where not necessary. My understanding was that USVStrings were not simply shorthand to avoid a pre-processing step, but a step forward to be able to avoid the issues related to unpaired surrogates where not needed. If I'm wrong, fine, I'm not trying to win an argument here, just get a better understanding of the issue. While not the default, I do see USVStrings being used in other APIs for things other that URLs, so if nothing else, the guidance about when to use one vs the other needs to be improved. 

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

Received on Thursday, 22 February 2018 19:47:56 UTC