70183 - "read" diamond shouldn't toggle on middle-click

Status: NEW

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Jesse Ruderman]

The "read" diamond in the mailnews thread pane currently toggles on left-, 
right-, or middle-click.  It should only toggle on left-click.

Comment 1

[Jesse Ruderman]

The thread triangle has the same problem.

Comment 2

[Håkan Waara]

All columns with an icon has the same problem throughout the app.

-> XP Toolkit: Trees

Comment 3

[Håkan Waara]

reassigning to default component owner.

Comment 4

[John Morrison]

threadPane.js/commandGlue.js explicitly toggles this on a click event. I 
don't think it is the tree's responsibility to "understand" the app's logic
(i.e., the click event happened and bubbled with the right event detail; 
the app can decide whether to ignore it). But this is all undergoing a port
to the outliner widget. back to mailnews/frontend

Comment 5

[(not reading, please use [e-mail] instead)]

I agree, this is our (the mailnews FE) job to handle.

we've had similar bugs (with double clicking on columns or the "green dot") that
we've handled in our JS.

accepting.

leave this with me until after the outliner branch lands.  fixing it on the
trunk before then would be a waste of work (and make merging harder).

Comment 6

[Travis Crump]

Don't understand what the "read" diamond is, but the thread triangle works for
me on Windows 2000 Build 20011208.  Middle-click does nothing, and right click
opens context menu.  However, middle clicking the speech bubble thingy
uncollapses the thread while right click on speech bubble thingy just opens the
context menu.  Figured out what the read diamond is, it is still broken(right
and middle clicks toggle it).

Comment 7

[Andreas Premstaller]

Using build 2002031403 on W2K, right click (and middle click, with Logitech
driver installed) does not toggle the read diamond any more, but shows (right
click) the context menu.

Comment 8

[Andreas Premstaller]

On Linux build 2002031508, right click only shows context menu on any element in
the message pane (this is correct behavior, I assume), middle click behaves as a
left click. 

Since right click works on Win and Linux, I change the summary accordingly.

On Mac OS9, build 2002031509, the situation is rather complex, input from some
Mac UI expert may be required. Here is what I observed:
<APPLE>+click just shows context menu for click on the threaded indicator (very
first column) and the read diamond, and first expands thread and then shows
context menu for click on the thread triangle. 
Click/hold first toggles the element for read diamond and expands thread for the
threaded indicator (so does normal click action), and then shows the context
menu. Click/hold on thread triangle does nothing on click, shows context menu
after some hold, and toggles between expanded and collapsed if mouse is released
still on the triangle.

Comment 9

[phil]

I don't know which bug depends on which, but I've filled Bug 203168 ("MIDDLE
mouse click scrolling in thread pane not working") closely related to this one.
Maybe Seth will re-organise these 2 bugs.

Comment 10

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 11

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 12

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 13

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 14

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 15

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 16

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420

Comment 17

[Karsten Düsterloh]

Still an issue, if middleclick is not configured to open a new tab.
Right click seems to be fixed, though.