292597 - the tree's currentIndex has a wrong value in some cases

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[soki]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217

There is a problem in the tree currentIndex. I developed an XBL with a tree wich
have some rows can be or cann't be selected (info given by RDF). I used
clearSelection() to erase the selection if a row cann't be selected. When the
tree have no focus because all items cann't be select (by clearSelection()) and
I try to open a "pivot" by clicking the icon, I obtain an error : 

Error: uncaught exception: [Exception... "Component returned failure code:
0x80070057 (NS_ERROR_ILLEGAL_VALUE) [nsITreeView.getParentIndex]"  nsresult:
"0x80070057 (NS_ERROR_ILLEGAL_VALUE)"  location: "JS frame ::
chrome://global/content/bindings/tree.xml :: onxblclick :: line 746"  data: no]

I had loooked the tree xbl file : tree.xml at the good line, and if the
currentIndex is bigger or egal at rowCount, there will be an error ! In my case,
and I don't know why, the myTree.currentIndex == myTree.view.rowCount... it
certainly a mistake in currentIndex gesture with no selection/focus. But if I
add a third test if the "if" clause, like "&& b.selection.currentIndex <
b.view.rowCount", I had no error. But the good correction should be in the
currentIndex gesture and not in the xbl tree file.

I cann't give my source, and I don't have time to make an exemple before 3 weeks.

Reproducible: Always

Steps to Reproduce:
Read details... no steps to reproduce

Comment 1

[[e-mail]]

CCing other people to help decide just how far we should validate currentIndex.

Comment 2

[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 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.