300668 - XUL custom treeview throws a permission denied error when selecting a row (non-chrome XUL)

Status: RESOLVED DUPLICATE of bug 209701

(Core :: XUL, defect)

Description

[daniel gurney]

User-Agent:       Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.8b2) Gecko/20050623 Firefox/1.0+
Build Identifier: Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.8b2) Gecko/20050623 Firefox/1.0+

See steps

Reproducible: Always

Steps to Reproduce:
1. Open the URL provided (a custom treeview example from XUL Planet)
2. Attempt to select a row
3. Notice that an exception is thrown:
Error: uncaught exception: Permission denied to create wrapper for object of
class UnnamedClass

The sample is not erring because of a TreeColumn being passed to the
"getCellText" method (instead of an ID-string), but due to some other factor.

Actual Results:  
Error: uncaught exception: Permission denied to create wrapper for object of
class UnnamedClass

Expected Results:  
The tree-view row should be selected, as in the default tree view control.

Comment 1

[Mark Porter]

Attachment: example

Code from the web site

Comment 2

[Mark Porter]

Attachment: example (correct)

first example had a syntax error.

I am getting the same effect in my own custom view backed trees, but only with
the  ff 1.5 beta 1

Comment 3

[Nickolay_Ponomarev]

So your problem is with non-chrome XUL trees, right?

Comment 4

[Mark Porter]

(In reply to comment #3)
> So your problem is with non-chrome XUL trees, right?

Yes it is, I haven't tried from chrome, but the UnnamedClass seems to only apply
to non-chrome xul.

Comment 5

[Mark Porter]

Attachment: example with work-around

This attachemnt is slightly modified to provide a nsISupports interface which
then reports that it supports nsITreeView. Code shamelessly stolen from: 

http://www.xulplanet.com/tutorials/xulqa/q_treebview.html

Is this an intentional change, or a bug?

Comment 6

[Alex Vincent [:WeirdAl]]

I believe this bug to cover the same issue as bug 209701.  Unlike this bug,
however, bug 209701 has at least an attempt at a patch.  I am therefore
resolving this bug as a duplicate of bug 209701.  Feel free to reopen if you
disagree.

*** This bug has been marked as a duplicate of 209701 ***