Closed Bug 89702 Opened 23 years ago Closed 23 years ago

[outliner] double clicking toggles open state, cause problems for folder pane / thread pane / select folder dialog

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
All
defect
Not set
major

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9.4

People

(Reporter: esther, Assigned: sspitzer)

References

Details

Using builds 2001-06-07 on win, mac and linux, if you have your thread pane sorted by thread and have a thread expanded, if you double-click on the 1st thread to view in a stand alone window, the thread collapses. 1. Launch Mail 2. Sort your Thread pane by thread and expand a thread. 3. Double-click on the 1st thread to bring up the msg in a stand alone window result: the thread for that message collapses in the tread pane expected: the thread to stay expanded
QA Contact: esther → nbaca
putterman: let's get this on the radar for an upcoming release. Setting to 0.9.4 - if you disagree, please feel free to comment.
Target Milestone: --- → mozilla0.9.4
Seth, this looks the same or similar to a bug you fixed last week regarding double clicking on the twisty.
no, this is a seperate bug. double clicking on a message that is the 1st message in a thread is toggling the expand / collapse state of the message.
Status: NEW → ASSIGNED
I think the problem is coming from outliner.xml in the double click handler, we have this: if (!cycler && obj.value != "twisty" && b.view.isContainer(row.value)) b.view.toggleOpenState(row.value); for mailnews, we don't want double clicking to toggle the twisty state. maybe this was added for outliners (bookmarks? filepicker? ftp?) hyatt, I can leave this as the default and add a call to get a specific attribute on the outlinerbody, and if that attribute is set to true, not toggle on double click. comments?
Summary: Expanded threads, collapse if 1st thread msg is opened in stand alone window → [outliner] double clicking toggles open state, cause problems for folder pane / thread pane / select folder dialog
hyatt gave me the info on how to do this. I need use addEventListener() to override this behaviour.
ok, thanks to hyatt and jan I've got this fixed for the thread pane and the folder pane in my local tree. I'll land it along with the fix for #73865. I'm using addEventListener() and event.preventBubble().
my fix for this has some weird side-effects. I'll probably land 73865 with out it, and fix this problem afterwards.
ok, the side effects weren't related. I'll land the fix for this with the fix for #73865.
*** Bug 94861 has been marked as a duplicate of this bug. ***
*** Bug 94997 has been marked as a duplicate of this bug. ***
fixed. for the folder pane, double clicking on a server should toggle the open / closed state, and should not open a new 3 pane. double clicking on a folder should not toggle the open / closed state, it should open a new 3 pane. for the thread pane, double clicking on a message in threaded mode should not toggle the open / closed state.
Status: ASSIGNED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Build 2001-08-15-04: WinMe Build 2001-08-15-08: Mac 9.04, Linux RH 6.2 Verified Fixed.
Status: RESOLVED → VERIFIED
This doesn't seem to be fixed for me on 2001-08-24-03. Win2K.
With 2001-08-24-03 on Win2K, I get exactly the response to a double click that Seth outlines above.
I'm not. I'm selecting a message at the top level of a thread that is expanded, double-clicking to open in a standalone message window, and seeing the thread collapse before the standalone message window spawns. That's the behavior we need to fix.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.