Closed
Bug 389868
Opened 17 years ago
Closed 17 years ago
Insert does not work properly when the insert location node is the root element of an instance
Categories
(Core Graveyard :: XForms, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 389016
People
(Reporter: jlc6, Unassigned)
Details
Attachments
(1 file)
1.67 KB,
application/xhtml+xml
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.5) Gecko/20070713 Firefox/2.0.0.5 Build Identifier: 0.8.0.3 If you try to insert an element into another element that is the root element of an instance, then the resulting behaviour does not follow the specification in one of two ways. In both of these cases, the `context` attribute is set and identifies the root element of the instance. If, first, the `nodeset` attribute is set and evaluates to the empty node-set, then the inserted node will overwrite the root element of the instance. If, on the other hand, the `nodeset` attribute is not specified, the insert action has no effect. Both results are incorrect; the node-set specified by `origin` should be inserted into the insert location node (which is the root element of the instance). Reproducible: Always
Reporter | ||
Comment 1•17 years ago
|
||
This attachment corresponds directly to the first example in section 9.3.5 of the XForms 1.1 working draft. In this case, the `nodeset` attribute is provided; this corresponds to the first trigger in the form. The `insert` action in the second trigger in the form does not provide the `nodeset` attribute; this demonstrates the second aspect of the bug described in this bug report.
Reporter | ||
Comment 2•17 years ago
|
||
After some additional testing, note that the bug also manifests when the insert location node is an element other than the root element of an instance (but the `nodeset` attribute still evaluates to an empty node-set). In this case, the origin node-set is inserted after the insert location node. Rule 6.a should apply in this situation, since "the Node Set Binding node-set is not specified or empty" (the latter), but the behaviour indicates, as in the the above case, that when the insert location node is the root element of an instance rule 6.c is being used, and that in the case described here rule 6.d is being used.
This looks like a dupe of bug 389016 and with that fix this testcase seems to work fine. If you still have problems after that patch goes in, please let us know.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•