Closed
Bug 148417
Opened 23 years ago
Closed 16 years ago
XUL trees misbehaving
Categories
(Core :: XUL, defect)
Core
XUL
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: arman, Assigned: janv)
Details
Attachments
(1 file)
|
994 bytes,
application/vnd.mozilla.xul+xml
|
Details |
There appears to be a general problem with the way event bubbling is happening
with trees. As the attached example shows, when stacking something on a tree,
the tree's children continue to show up and consume events. However, the tree
columns seem to work properly. I believe this problem showed up as of RC3 and
also occurs in the latest nightly.
A sub-problem of this bug is that it prevents proper handling of drag-drop
events. For instance, dropping something on the area of the tree column header
beheaves as expected. But, dragover in other areas is rejected.
Comment 2•23 years ago
|
||
1) Does this bug still happen on a recent nightly? I couldn't tell, because:
2) Could you give us steps to reproduce the bug with the test case?
3) Could you give us an "Expected Results" and "Actual Results"?
-M
Comment 3•23 years ago
|
||
*SPAM*: CC'ing myself.
In reply to your questions:
* Yes the bug is still there in the latest nightly.
* To reproduce, just view the (XUL tree events problem) attachment in Mozilla.
* The expected result is that tree's components should not be visible as they
are stacked underneath the button. i.e. We should only be able to see and
interact with a large button on the screen. The actual result is that I see the
tree items and I'm able to click on and select them.
Comment 5•23 years ago
|
||
Confirming. Jan, could you take a look at this? Happens on Linux too.
Assignee: hyatt → varga
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 2000 → All
Hardware: PC → All
Component: XP Toolkit/Widgets: XUL → XUL
QA Contact: shrir → xptoolkit.widgets
Comment 6•16 years ago
|
||
No longer valid I think.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•