157217 - [SM] META BUG for 3 pane window issues

Status: NEW

(SeaMonkey :: MailNews: Message Display, defect)

Description

[racham]

This is a meta bug for all bugs related to mailnews 3 pane window. This bug will
be used for tracking purposes. Please post contributions (patches) & ideas in
corresponding bugs.

Comment 1

[racham]

The current list is not all 3 pane bugs we have today. There are more. I will be
adding more going forward.

Comment 2

[Greg K.]

Adding meta. Any reason this shouldn't be All/All?

Comment 3

[Olga]

Added more bugs. Other meta bugs for Mail: 
Bug 155643 - Drag and Drop within mailnews 
Bug 154225 - Proper messages to be displayed to the user by the mailnews system
Bug 154249 - Mailnews Front End accessibility (except mnemonics)
Bug 129179 - Mnemonics in Mail & Browser
Bug 154188 - Tracker for Compose polish and focus bugs
Bug 158011 - Context menu issues for Mail&Newsgroups
Bug 77232 - Big problems with Search Messages UI
Bug 77248 - Big problems with Message Filters UI
  


 

Comment 4

[FZiegler]

Tentatively adding (but feel free to shoot it down if you disagree):

bug 114637 - can't drag-select in thread pane

See also...

bug 160730 - META Bug for 3 Pane Mail; polish, correctness, UE stuff 

Comment 5

[Olga]

Added keyword nsbeta1 to 8 UI Mailnews meta bugs.

Comment 6

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

mass re-assign.

Comment 7

[Robert Kaiser]

MASS-CHANGE:
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 8

[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 9

[Karsten Düsterloh]

Still a valid meat bug!