- From: <bugzilla@jessica.w3.org>
- Date: Thu, 30 Sep 2010 19:22:16 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10878 --- Comment #2 from Jonas Sicking <jonas@sicking.cc> 2010-09-30 19:22:16 UTC --- I don't think that this will cause any problems to Gecko. Structured cloning is used very rarely so far, and I strongly suspect that most of the time people use very simple objects that won't be affected by this change. In fact, most of the time we use JSON behind the scenes, and so far no one has noticed the difference. This is changing though, so we will be using a custom structured-clone implementation soon. The only requirement we have is that a structured-clone-able object can be serialized and serialized both quickly and with little overhead. This is needed for example in IndexedDB where we need to serialize the object to be able to store it in the database for later retrieval. Similarly we need to serialize and parse the object when passing data to workers. -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 30 September 2010 19:22:18 UTC