Open
Bug 391574
Opened 17 years ago
Updated 2 years ago
Position of text field not correct when editing individual tree cells (if horizontally scrolled)
Categories
(Core :: XUL, defect)
Tracking
()
UNCONFIRMED
People
(Reporter: westbluz, Unassigned)
Details
Attachments
(2 files)
5.82 KB,
application/vnd.mozilla.xul+xml
|
Details | |
2.31 KB,
patch
|
Details | Diff | Splinter Review |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; sl; rv:1.8.1.6) Gecko/20070725 Firefox/2.0.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a7) Gecko/2007080210 GranParadiso/3.0a7
Position of text field is not located correctly when editing individual tree cells if the tree is scrolled horizontally.
Reproducible: Always
Steps to Reproduce:
1.Create a tree with the horizontal scroller active.
2.Enable editing of individual cells.
3.Scroll horizontally and double-click on an editable cell.
Actual Results:
Position of the text field is not aligned with a tree column.
Expected Results:
Position of the text field should be aligned with a tree column.
getCoordsForCellItem method also doesn't work if horizontally scrolled. It returns 0 for x and y cords.
Comment 3•17 years ago
|
||
This bug is probably related to bug 392216 which deals with *vertical* scrolling.
I hope Jan can get around to looking into it b/f Firefox 3 though.
Comment 4•17 years ago
|
||
Bug 399961 is actually being worked on which fixes a similar issue with in nsTreeBodyFrame.cpp, the getCellAt function.
In this case it's the getCoordsForCellItem that's messing up. I'll attach a temporary workaround to this for anybody who's interested but that's all it is: temporary. The bug lies in fixing getCoordsForCellItem.
Comment 5•17 years ago
|
||
Updated•17 years ago
|
Attachment #288110 -
Attachment is patch: true
Attachment #288110 -
Attachment mime type: application/octet-stream → text/plain
Component: XP Toolkit/Widgets: Trees → XUL
QA Contact: xptoolkit.trees → xptoolkit.widgets
Comment 6•6 years ago
|
||
The plan is to remove the XUL "tree" widget in future (bug 1446335), but this has a patch, so for now I'm not going to wontfix this.
Assignee: jvarga → nobody
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•