This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/origin-0.html Multipage: http://www.whatwg.org/C#dom-document-domain Complete: http://www.whatwg.org/c#dom-document-domain Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/dom.html Comment: Unclear about Unicode vs ASCII serialization Posted from: 178.83.154.60 by annevk@annevk.nl User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:33.0) Gecko/20100101 Firefox/33.0
Can you elaborate?
When you get document.domain, it's unclear how the domain is to be serialized.
It isn't. The attribute's value is "the document's domain", which is a string.
Fair. Then the question applies to "the document's domain". But we might need to expose different strings in different places I suspect due to legacy.
"the document's domain" is set from the "host" component of the origin tuple, which is also a string, and which is set in a variety of places. Are any of those places ambiguous? If they are, we have a much bigger problem on our hands since that affects the security model.
I guess that's fair, so they should all be ASCII then per default parsing rules.