Closed
Bug 17129
Opened 25 years ago
Closed 25 years ago
[Tree] Double click on tree scrollbar launches item in bookmarks
Categories
(SeaMonkey :: Sidebar, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M13
People
(Reporter: MatsPalmgren_bugz, Assigned: hyatt)
References
Details
TO REPRODUCE:
1. start mozilla, open sidebar
2. double-click (left mouse button) an arrow button in the scrollbar in the
"Bookmarks" panel in the sidebar.
ACTUAL:
file:///C|/MOZILLA-1999-10-22-09-M11/BIN/chrome/bookmarks/content/default/bookma
rks.xul
is loaded in to content area.
EXPECTED: two single click actions (compare with native scrollbar)
VERSION & OS:
Mozilla nightly build 1999-10-22-09-M11 on Windows 98 SE.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Updated•25 years ago
|
Target Milestone: M12
Comment 1•25 years ago
|
||
This is weird I see this too. Maybe hyatt can help me solve this.
Reporter | ||
Comment 2•25 years ago
|
||
Another way to trigger (what I think is) the same bug is to:
1. open the "Manage Bookmarks" window
2. double-click on a column header ("Name" or "URL")
This will open a new window.
Double-clicking the +/- handles also has this effect...
Comment 3•25 years ago
|
||
I have a fix for the bookmark headers. It seems to be a different problem than
the scrollbars.
The fix is to move the onclick handler on the tree node and move it to the
treechildren.
Updated•25 years ago
|
Assignee: slamm → alecf
Status: ASSIGNED → NEW
Summary: bookmarks.xul is loaded if double clicking scrollbar arrow button → Double click on tree scrollbar launches item in bookmarks
Comment 5•25 years ago
|
||
Reassigning to alecf. He is working on trees now.
Updated•25 years ago
|
Status: NEW → ASSIGNED
Summary: Double click on tree scrollbar launches item in bookmarks → [Tree] Double click on tree scrollbar launches item in bookmarks
Comment 6•25 years ago
|
||
need to spend 5 minutes investigating this, probably a M13 candidate.
Updated•25 years ago
|
Target Milestone: M12 → M13
Comment 7•25 years ago
|
||
argh, this looks like another event problem, probably related to #15112, since
it is once again dom events that are firing when they're not supposed to...
it seems like onclick events are being generated even though they are supposed
to be consumed by the toplevel button. Adding evaughan and joki for advice.
Moving to M13
Comment 8•25 years ago
|
||
Can someone point me to the button which is supposed to consume this event so I
can look at it? From looking at the path into the scrollbarbuttonfrmae I'm not
seeing any action here which would affect the next event.
Comment 9•25 years ago
|
||
I was poking at this yesterday, I'll try to get more details.
Assignee | ||
Comment 10•25 years ago
|
||
This is a dup of another bug... the one that says "Anonymous DOM node events
shouldn't bubble."
Comment 11•25 years ago
|
||
just searched for that, haven't found it yet.
Updated•25 years ago
|
Assignee: alecf → waterson
Status: ASSIGNED → NEW
Comment 12•25 years ago
|
||
Looks like the other bug is bug 9029, which waterson marked invalid. So I'm
reassigning this one to him :-) Alecf reports that this symptom is still happening.
Updated•25 years ago
|
Assignee: waterson → alecf
Comment 13•25 years ago
|
||
this is a problem with events "getting through" the scrollbar frame and being
processed by the underlying treerow. The frame code is in charge of dispatching
those events, and alecf is in charge of the frame code.
Comment 14•25 years ago
|
||
*** Bug 21587 has been marked as a duplicate of this bug. ***
Updated•25 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Updated•25 years ago
|
Assignee: alecf → hyatt
Status: ASSIGNED → NEW
Assignee | ||
Updated•25 years ago
|
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 15•25 years ago
|
||
I fixed this.
Assignee | ||
Comment 16•25 years ago
|
||
Fixed.
Updated•25 years ago
|
Status: RESOLVED → VERIFIED
Comment 17•25 years ago
|
||
looking good, 1/11 builds
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•