tree control doesn't work.

Tree control doesn't work in FF, how can you expect people to pay for this stuff?

What do you find that doesn't work? You have to be a little more descriptive if you want anyone to help you. I have not seen any problems with it. What version of FF are you using? Have you tried the Controls.htm demo to see how it looks on your browser?

Well I used the demo on the website here linked to the documentation page for the tree control, which I assume is the same one.

What happens is that instead of opening and closing the tree elements, clicking on them causes them to get duplicated over and over, once for each click.

It works fine in IE. I have made plenty of tree controls in my day, and I know they *can* work in FF... in fact I'm working on an app right now that uses one with FF.

oh, FF 1.0.7 on this machine... I was on a linux box earlier with the lastest nightly snapshot of FF and observed the same behavior.

My test results yield

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1

WORKS - Everything seems to be OK

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.12) Gecko/20051010 Firefox/1.0.7 (Ubuntu package 1.0.7)

NO WORKY :( - Tree nodes spawn out of nowhere and start duplicating themselves.

Much better information, thanks! Since I only use FF 1.5 I have not seen this behavior. I have heard of many issues with the Ubuntu build. From what I have seen, I would say that it is not a supported version at this time as there are too many issues with it. Since there are so many problems with it, I would have to wager a guess and say that the problem lies in FF and not in the AW code. Just my opinion...

Odd, I wonder what Ubuntu is doing to the FF source? I wasn't aware it was customized in that distro, I run Gentoo myself. I just download the source directly from mozilla.org and compile it.

compiler = gcc 3.4.4
platform = alpha (ev56)

Perhaps I should compile a copy of FF 1.5 and try with that...

Yep, it works in FF 1.5.0.1

1.0.7 must have some sort of CSS issue.