392216 - Position of text field not correct when editing individual tree cells (if vertically scrolled)

Status: RESOLVED WONTFIX

(Core :: XUL, defect)

Description

[Mime Čuvalo]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a7) Gecko/2007080210 GranParadiso/3.0a7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a7) Gecko/2007080210 GranParadiso/3.0a7

When there are enough treerows and the tree is scrolled, editing a cell will cause the tree to resize and the cell being edited will jump around to another position.

Reproducible: Always

Steps to Reproduce:
1. Open test case attachment.
2. Scroll to the bottom.
3. Double-click to edit.
Actual Results:  
Resizes tree more and more drastically the further you scroll down.  The treecell being edited jumps to an incorrect position.

Expected Results:  
Shouldn't resize the tree and show treecell in incorrect position.

Comment 1

[Mime Čuvalo]

Attachment: Testcase

Comment 2

[Mime Čuvalo]

Attachment: Screenshot

Comment 3

[Mime Čuvalo]

I'm still seeing this on the trunk - could you take a look, Jan?

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a9pre) Gecko/2007101104 Minefield/3.0a9pre

Comment 4

[Mime Čuvalo]

I see that this bug is related to bug 391574

Comment 5

[:Mook]

I'm sorry, but I thought this was about the fact that the whole tree gets moved around? (not just having a misplaced edit box)  Whereas bug 391574 is about the edit box being incorrectly positioned (horizontal or vertical; it looks like it's mixing coordinate systems)

Having the tree move around is harder to work around via CSS :)

Comment 6

[Mime Čuvalo]

(In reply to comment #5)
> I'm sorry, but I thought this was about the fact that the whole tree gets moved
> around? (not just having a misplaced edit box)  Whereas bug 391574 is about the
> edit box being incorrectly positioned (horizontal or vertical; it looks like
> it's mixing coordinate systems)
> 
> Having the tree move around is harder to work around via CSS :)
> 

Ha, yeah I guess - should I rename it back?  I think it's a combination of the two though.  Can't be sure though.

Comment 7

[Mime Čuvalo]

(In reply to comment #5)
> Having the tree move around is harder to work around via CSS :)

I forgot to ask - does that you mean you have a work around maybe? :)  I could use something until this gets fixed.

Comment 8

[Mime Čuvalo]

Well, for anybody who's interested: I'm working around this by just removing the flex="1" attribute on the box below the splitter and replacing it with height="150" and persist="height" attributes.

Comment 9

[Jan Varga [:janv]]

I don't think anyone is going to work on this given the plan to remove the XUL "tree" widget (bug 1446335).