420272 - Before the first selection event occurred the tree element incorrectly reports its currentIndex as 0.

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Sebastian Winkler]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10_4_11; en) AppleWebKit/526+ (KHTML, like Gecko) Version/3.0.4 Safari/523.12.2
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.4; en-US; rv:1.9b4pre) Gecko/2008022804 Minefield/3.0b4pre

In Firefox the currentIndex property of the tree element seems to be incorrectly initialized to 0 instead of -1.
I've tested this in FF on Windows and OSX: both give 0 instead of -1.
Camino correctly reports -1.

I'll attach a test case

Reproducible: Always

Steps to Reproduce:
1. Open the test case 'currentIndex_testcase.xul'
2. Click on the empty area of the tree, before having selected any of the treeitems
Actual Results:  
The tree's currentIndex property is reported as 0.

Expected Results:  
The tree's currentIndex property should be -1.

Comment 1

[Sebastian Winkler]

Attachment: Testcase: xul document containing a tree which upon clicking reports its currentIndex property

Comment 2

[Sebastian Winkler]

Attachment: Revised testcase: added buttons to query and remove the selection from outside the tree

Comment 3

[Sebastian Winkler]

I've attached a second similar testcase with a button which will get the tree by id and then alert its currentIndex.
Interestingly, if pressed before clicking the tree, the result differs from the one that the onclick handler on the tree itself, using this.currentIndex, produces, correctly reporting -1. After clicking the tree the button presents the same result.
In this testcase one also learns that nsITreeSelection.clearSelection() doesn't seem to reset the currentIndex to -1, which, I suppose, it should.
Anyway, the issue doesn't seem to be related to the tree selection being incompletely or incorrectly initialized after all as it also occurs after calling clearSelection or selection -1.

Comment 4

[Tyler Downer [He/Him]]

This is a mass search for bugs that are in the Firefox General component, are
UNCO, and have not been changed for 800 days and have an unspecified version. 

Reporter, can you please update to Firefox 3.6.10, create a fresh profile,
http://support.mozilla.com/en-US/kb/managing+profiles, and test again. If you
still see the bug, please update this bug. If the issue is gone, please set the
resolution to RESOLVED > WORKSFORME.

Comment 5

[Tyler Downer [He/Him]]

No reply from reporter, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.