W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2014

[Bug 24581] Fix ByteString type & [EnsureUTF16] flag story

From: <bugzilla@jessica.w3.org>
Date: Tue, 24 Jun 2014 13:21:02 +0000
To: public-script-coord@w3.org
Message-ID: <bug-24581-3890-UcZcgaWATW@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24581

Domenic Denicola <domenic@domenicdenicola.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |domenic@domenicdenicola.com

--- Comment #7 from Domenic Denicola <domenic@domenicdenicola.com> ---
> 3. An attractive name such as UnicodeString might lead to adoption in places that do not require it. String/DOMString should be used normally.

I just want to second this. As an API designer, if presented with the choice
between `UnicodeString` and `DOMString`, I'd probably choose UnicodeString.
("Of course I want to support Unicode! I bet whatever a DOMString is, it's to
support some weird legacy DOM APIs.")

I don't see why ScalarValueString is bad, really, despite the stated reasons.
But if this must change for whatever reason, it needs to sound "weird." Maybe
PostprocessedUnicodeString or ScalarizedUnicodeString or something.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Tuesday, 24 June 2014 13:21:04 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:22 UTC