This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 11091 - Clarify whether importNode copies the 'already executed' flag
Summary: Clarify whether importNode copies the 'already executed' flag
Alias: None
Product: HTML WG
Classification: Unclassified
Component: LC1 HTML5 spec (show other bugs)
Version: unspecified
Hardware: All All
: P1 critical
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
Depends on:
Reported: 2010-10-19 12:38 UTC by Henri Sivonen
Modified: 2011-08-04 05:00 UTC (History)
4 users (show)

See Also:


Description Henri Sivonen 2010-10-19 12:38:27 UTC
In Gecko, it seems the 'already executed' flag is copied. In WebKit, it seems it isn't copied.

Opera seems to execute the script because 'already executed' hasn't been set in the first place:

IE9 beta1 seems to be unable to either adopt or import nodes from a non-ActiveX XHR doc into a doc in a browsing context.

Please define the correct behavior for importNode in this case. In any case, it would be a bad idea to copy the 'parser-inserted' flag.
Comment 1 Ian 'Hixie' Hickson 2010-12-26 20:18:21 UTC
importNode() doesn't do anything at all, does it? I thought we were dropping that API entirely as a no-op.
Comment 2 Simon Pieters 2010-12-27 09:33:13 UTC
"The importNode(node, deep) method must return a clone of node, with new ownerDocument being the context node, and the clone children flag set if deep is true."
Comment 3 Ian 'Hixie' Hickson 2011-02-09 00:42:34 UTC
Oh, right, I was thinking of adoptNode().

EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:

Status: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments. (I made it the same as cloneNode(), for sanity.)
Comment 4 contributor 2011-02-09 00:43:33 UTC
Checked in as WHATWG revision r5863.
Check-in comment: Clarify that the cloning that occurs for importNode() is the same as occurs for cloneNode().
Comment 5 Michael[tm] Smith 2011-08-04 05:00:38 UTC
mass-moved component to LC1