289664 - Need a way to get explicit children with insertion point at anonymous node

Status: RESOLVED WONTFIX

(Core :: XBL, defect)

Description

[alexander :surkov (:asurkov)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; ru-RU; rv:1.7.5) Gecko/20041108 Firefox/1.0 (ax)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8b) Gecko/20050217

<binding id="bnd1">
<content>
  <box>
    <children/>
  </box>
</content>
</binding>

<bnd1>
  <box/>
</bnd1>

There should a way to get explicit children inserted at anonymous node 'box' of
binding 'bnd1'. When I try box.childNodes then I'm fail.

I seem after proccessing <children> explicit children of bound element should be
explicit children of anonymous node, i.e. I should be able to get explicit
children of bound element by using childNodes() method of anonymous node.

<binding id="bnd2">
<content>
  <children/>
</content>
</binding>

In this case I'm able to get explicit children of bound elememnt by two ways:
1) by using childNodes()
2) by using document.getAnonymousNodes(boundelm)

After proccessing <children> tag explicit children of bound element are
anonymous nodes too. And so why explicit children of bound element is not
explicit children of anonymous node (see the first example)? Is it a bug or
right behaviour?

If it is right behaviour then I suppose the only way to get explicit children is
using of xblNode (http://www.w3.org/TR/sXBL/#nodexbl0) interface of sXBL
specification. Is it right? What should childNodes() method return in accordance
 with sXBL specification?

Reproducible: Always

Steps to Reproduce:

Comment 1

[alexander :surkov (:asurkov)]

Cc'ing bz.

Comment 2

[Boris Zbarsky [:bzbarsky]]

> After proccessing <children> tag explicit children of bound element are
> anonymous nodes too.

Actually, no.  They are not.

> And so why explicit children of bound element is not
> explicit children of anonymous node (see the first example)?

Because they're still kids of the bound element.  Each node is in one and only
one place in the DOM.

> What should childNodes() method return in accordance with sXBL specification?

All DOM Core methods should be returning exactly what they would return if there
were no XBL around.  sXBL is pretty clear on this.

Note bug 284002

Comment 3

[Boris Zbarsky [:bzbarsky]]

Oh, and I watch [e-mail], so no need to cc me on XBL bugs... I get the
mail anyway.

Comment 4

[alexander :surkov (:asurkov)]

Comment#2
>> After proccessing <children> tag explicit children of bound element are
>> anonymous nodes too.

>Actually, no.  They are not.

Why not? If document.getAnonymousNodes(this) returns the scope of explicit
children (like example#2 of comment#0) then explicit children is anonymous
nodes. I can attach a testcase to show this.

Comment#3
I will not.

Comment 5

[Boris Zbarsky [:bzbarsky]]

What getAnonymousNodes does is pretty murky (and likely to be buggy in various
cases)....  Ideally it'll go away in favor of the NodeXBL interfaces.

Comment 6

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 7

[alexander :surkov (:asurkov)]

(In reply to comment #5)
> What getAnonymousNodes does is pretty murky (and likely to be buggy in various
> cases)....  Ideally it'll go away in favor of the NodeXBL interfaces.

Should we mark the bug as worksforme and wait for fixing of bug 284002?

Comment 8

[Boris Zbarsky [:bzbarsky]]

XBL is now disabled in Firefox (Bug 1583314) and is in the process of being removed from Gecko (Bug 1566221), so closing bugs requesting changes to its implementation as wontfix.