- From: <bugzilla@jessica.w3.org>
- Date: Mon, 17 Mar 2014 16:02:26 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24208 --- Comment #5 from Victor Costan <costan@gmail.com> --- I'm terribly sorry for answering to this so late! My inbox ate your reply, and I just happened to check on this bug today. The hash function that I'm relying on right now is consistent within a browser process, but may change across platforms and browser versions. I like your approach for having a resilient spec, and have one minor mention. It might be better to allow the hash code to be up to 20 digits in length, to allow UAs to use 64-bit hashes. I agree that this might be overkill. You can always spec that serialization should throw an exception in this case, and I'd be happy to implement just that :) I don't think this should break too much of the Web, because right now Chrome and Safari basically generate invalid XML in this case. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Monday, 17 March 2014 16:02:27 UTC