- From: <bugzilla@jessica.w3.org>
- Date: Thu, 02 Oct 2014 17:51:52 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=14086 brunoais <brunoaiss@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED CC| |brunoaiss@gmail.com Resolution|WONTFIX |--- --- Comment #16 from brunoais <brunoaiss@gmail.com> --- I'd like to revive this bug and ask for a minor alternative that might be possible and OK to go for. The idea is to allow passing document fragments to worker threads (document fragments only). The main idea is that, sometimes, a large amount of changes or analysis are required to be made to the DOM. By allowing sending a fragment to a worker thread, the overhead required to translate all the DOM send into an analyzable format. You may even require http://www.w3.org/TR/DOM-Level-2-Core/core.html#Core-Document-importNode Or some work adapting the content to the worker. As long as that is made in the other thread, there's no issue on my end. The requirements for my use-case are: --- Having a nearly complete document DOM --- This document is not connected to any interface. In other words, it acts the same way as a documentFragment towards everything (heck, it can even be an actual documentFragment, if possible). Any changes to it only changes that DOM tree inside the worker thread. --- You can pass DOM objects --- A passed DOM object is read-only on the destination until http://www.w3.org/TR/DOM-Level-2-Core/core.html#Core-Document-importNode is called. OR Passing a DOM is made by cloning it to the document that resides in the worker thread. The result of that clone is equivalent of passing it through the importNode() method. (I prefer the 2nd one) If this is enabled, when the parsing work on the js side is more complicated, it may be sent to the worker thread to deal with the specifics and still have tree-like operations with Nodes that look like the interface's DOM. -- You are receiving this mail because: You are on the CC list for the bug.
Received on Thursday, 2 October 2014 17:51:54 UTC