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

Servo wasn't part of the discussion. This was based on my recollection of DOMString vs USVString discussions we had in the TAG a while back. I accept that I may have mis-remembered, was simply wrong, or that the consensus on which to use has moved on since those discussions and I was out of the loop.

My understanding is that the primary difference between a DOMString and a USVString is that the former allows unpaired surrogates while the latter does not. My recollection was that allowing unpaired surrogates was a legacy mistake that we're stuck with in older APIs, but didn't want to propagate to new APIs, and that USVString should be preferred for new work where compatibility with older APIs wasn't an issue, not just for URLs. Hence this decision.

If I'm wrong, we can revisit/revert this decision (and should make the guidance in WebIDL clearer and/or add a section the the TAG's design principles document to prevent this mistake in the future). If there's still debate on this, then we should file an issue on the TAG and get better consensus on how to proceed.



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

Received on Thursday, 22 February 2018 06:02:04 UTC