[Webkit-unassigned] [Bug 64860] New: Script element created with Range.createContextualFragment is not executed
bugzilla-daemon at webkit.org
bugzilla-daemon at webkit.org
Wed Jul 20 04:09:49 PDT 2011
https://bugs.webkit.org/show_bug.cgi?id=64860
Summary: Script element created with
Range.createContextualFragment is not executed
Product: WebKit
Version: 525.x (Safari 3.2)
Platform: All
OS/Version: All
Status: UNCONFIRMED
Severity: Normal
Priority: P2
Component: HTML DOM
AssignedTo: webkit-unassigned at lists.webkit.org
ReportedBy: martingrigorov at yahoo.com
Chrome Version : 14.0.814.0 dev
URLs (if applicable) : See attached
Other browsers tested:
Add OK or FAIL after other browsers where you have tested this issue:
Safari 5: FAIL
Firefox 4.x: OK
IE 7/8/9: FAIL
Opera 11.x: OK
What steps will reproduce the problem?
1. Put the attached .html in a folder under www root.
2. Open it in the browser (e.g. http://localhost/tmp/execute-script.html
What is the expected result?
The 'Old element' DIVElement is replaced with a new ScriptElement and the body of the script element is executed. I.e. an alert with text 'executed' should be shown.
What happens instead?
The div element is replaced but the the script body is not executed.
Please provide any additional information below. Attach a screenshot if
possible.
This JavaScript snippet is used to replace an element with a new one by creating a fragment from a text and replacing the old element with the fragment.
The attachment is simplified - it replaces div with script but in a real application it could be another div with many children one of which is a script.
Firefox and Opera support completely this functionality. WebKit based browsers replace the elements but doesn't execute the script body. Internet Explorer doesn't support range.createContextualFragment() at all.
Bug report for Chromium: http://code.google.com/p/chromium/issues/detail?id=89694
--
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