[Webkit-unassigned] [Bug 38984] document.documentElement cannot be replaced

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Wed May 12 17:31:45 PDT 2010


https://bugs.webkit.org/show_bug.cgi?id=38984





--- Comment #7 from gildas <gildas.lormeau at gmail.com>  2010-05-12 17:31:45 PST ---
(In reply to comment #6)
> Confirmed with r59249.
> 
> One more question: why is this important? WebKit isn't really prepared for such drastic changes to an existing document, so this may not be an easy fix.

Actually, I have done an extension for chrome which does heavy DOM modifications to embed all external resources into the page. Here is the extension link :
https://chrome.google.com/extensions/detail/mpiodijhokgodhhofbcjdecpffjipkle/publish-accepted

It's really better to do all those DOM modifications in a cloned DOM for speed issue (because the browser do not have to render DOM modifications). The extension have no issues to embed images, css, frames resources but when the extension try to embed an external script into the documentElement node, the issue appears. In this case, the only way I found to bypass this issue is to work directly on the document.documentElement.

I think it may be a small bug since scripts are the only resources that cause this issue. 

Also, I think Rich Text Editors may suffer from this issue.

-- 
Configure bugmail: https://bugs.webkit.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the webkit-unassigned mailing list