335526 - XUL: crash when setting a "command" attribute on a newly created element

Status: RESOLVED INCOMPLETE

(Core :: XUL, defect)

Description

[Frederic Bonjour]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2

I am developping an application with XUL. Depending on the selected elements of a tree, I dynamically create <toolbarbutton>s on which I set the "command" attribute to an existing <command> ID (this ID has the following format: "command:<the-command-id>:sometext"). The code that creates these toolbarbuttons is inside a binding and these buttons are appended to an element inside this binding.

Here is some pieces of code to clarify this:

In my XUL file:
----
<command id="command:delete:mainTree" label="Delete" oncommand="..." />
----

In a method of my binding:
----
var item = document.createElement("toolbarbutton");
item.setAttribute("command", "command:delete:mainTree");
var container = document.getAnonymousElementByAttribute(this, "anonid", "container");
container.appendChild(item);
----

In the "content" of my binding:
----
<toolbar anonid="container" />
----

Of course, the code is a bit more complex but I can't write it all here: it uses braodcasters, observers to detected changes in the elements list...

Hope it's quite clear...



Reproducible: Always

Actual Results:  
Crashes without any error message neither in the JavaScript console not in the console (when launched with "-console").

Expected Results:  
No crash ;-)

Comment 1

[Martijn Wargers (dead)]

Do you have a talkback ID? Could you give one?

Comment 2

[Nickolay_Ponomarev]

Also please check if this happens with a trunk build.

Comment 3

[Frederic Bonjour]

Attachment: The "details" information provided by the TalkBack when the crash happened

Comment 4

[Nickolay_Ponomarev]

That's not what we need. See http://kb.mozillazine.org/Talkback

Comment 5

[Tanner M. Young [:tmyoung]]

Is this still an issue in Firefox 3.5?

If it is not, we should set the resolution of the bug to WORKSFORME.

Comment 6

[Nickolay_Ponomarev]

Since the bug is old, we don't have any information in it that can lead to a fix (testcase and crash stack) and the reporter doesn't reply, closing as incomplete.

If someone can reproduce in recent Firefox builds and can provide the testcase or the crash report, feel free to reopen or file a new bug.