20159 2012-11-29 14:58:58 +0000 Introduce attributes for DOMString coercion 2014-11-17 18:37:34 +0000 1 1 1 Unclassified WebAppsWG WebIDL unspecified PC Windows 3.1 RESOLVED DUPLICATE 24581 P2 normal --- 1 annevk cam bzbarsky mike public-script-coord public-webapps-bugzilla oldest_to_newest 79123 0 annevk 2012-11-29 14:58:58 +0000 1) An attribute that converts lone surrogates to U+FFFD as per http://lists.w3.org/Archives/Public/public-script-coord/2012OctDec/thread.html#msg82 2) An attribute to replace ByteString. We should probably not have ByteString as a distinct type per the arguments from Brendan in the thread above. 79128 1 bzbarsky 2012-11-29 16:11:37 +0000 I would actually prefer a distinct type for ByteString. On the C++ side, ByteString needs to become some version of char*, while DOMString becomes a Unicode string. These are typically different C++ classes, not just different conversion code. And while it's possible to change the actual type of the object based on extended attributes, it feels pretty weird. 115024 2 annevk 2014-11-17 18:37:34 +0000 *** This bug has been marked as a duplicate of bug 24581 ***