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

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

From: <bugzilla@jessica.w3.org>
Date: Fri, 03 Oct 2014 08:32:51 +0000
To: public-script-coord@w3.org
Message-ID: <bug-24581-3890-zzKsQG6Wod@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24581

Cameron McCormack <cam@mcc.id.au> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #11 from Cameron McCormack <cam@mcc.id.au> ---
(In reply to Anne from comment #10)
> That works for me. Is there any ETA on when this will land in IDL? If it's
> going to take long I could rename this in various places before I go away
> most of July.

Oops, it's October already. :-(

I agree that "Unicode" might well be an attractive nuisance, particularly if
"String" is also in the name.

I've gone with "USVString".  You can now also use string literals for optional
argument and dictionary members of any of the string types.

https://github.com/heycam/webidl/commit/672e73d476d8c4341339cc22592bb5ff01c69823

http://heycam.github.io/webidl/#idl-USVString
http://heycam.github.io/webidl/#es-USVString
http://heycam.github.io/webidl/#string-literal
http://heycam.github.io/webidl/#dfn-overload-resolution-algorithm
http://heycam.github.io/webidl/#es-union

Let me know if this is sufficient.  Thanks!

This means we can remove [EnsureUTF16], yes?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 3 October 2014 08:32:53 UTC

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