Bug 17044 - Cloning algorithm doesn't indicate that the "already started" flag needs to be cloned for script elements
Summary: Cloning algorithm doesn't indicate that the "already started" flag needs to b...
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: DOM (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-14 08:22 UTC by Henri Sivonen
Modified: 2012-05-15 10:48 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henri Sivonen 2012-05-14 08:22:58 UTC
If you read the "clone" algorithm in the DOM Core spec, you won't find a normative statement saying that you have to clone the "already started" flag on script elements.  To make sure that readers of the spec find the right normative statement, please provide an informative pointer to http://www.whatwg.org/specs/web-apps/current-work/#already-started

Please weasel in some language to suggest that SVG script elements should work consistently with HTML script elements in this regard.
Comment 1 Anne 2012-05-14 10:20:17 UTC
HTML also does this for input elements. Not sure where else. I guess we should try to keep the note exhaustive although that does kind of argue for just writing these things in DOM directly...