134636 - Partially Displayed Message Header Not Selectable in Header Pane

Status: VERIFIED DUPLICATE of bug 134889

(SeaMonkey :: MailNews: Message Display, defect)

Description

[Felix Miata]

2002033108 OS/2 [not new, but can't recall when first noticed]

Steps to reproduce:
1-In normal three pane view
2-Using fresh migration with none of the three panes ever resized, though
overall mailnews resized to nearly full width of screen, and somewhat taller
than defaul
3-Showing in headers pane approximately 5.98 headers
4-Open newsgroup with more message headers than can be displayed at once

Actual behavior: when as little as one pixel of the bottom message header is
hidden by the edge of the pane, the bottom header cannot be selected until the
window is scrolled up to expose every pixel of that message header.

Expected behavior: if any portion of a message header is showing it should be
selectable.

Comment 1

[Mike Kaply [:mkaply]]

Not OS/2 specific

Comment 2

[Leston Buell]

Attachment: screenshot: last selectable message

In this screenshot, the message header below the one selected cannot be
selected, even though it is almost entirely visible.

Comment 3

[Lasse Marøen]

This was OK a couple of days ago. Adding regression keyword.

Comment 4

[Lasse Marøen]

This is really a bug in outliner. Same bug is in manage bookmarks, folder pane,
etc. And it's already filed. Resolving as duplicate..

*** This bug has been marked as a duplicate of 134889 ***

Comment 5

[Felix Miata]

1-Why does a senior bug (this) get marked as a duplicate of a newer bug
(134889)? I've asked this before and didn't get an answer.

2-I can't find a program or component named outliner. What is outliner? Bug
134889 doesn't provide a definition.

Comment 6

[[e-mail] (gone - use [e-mail] instead)]

Outliner is a widget.  <outliner>foo</outliner> used to be the syntax, but Joe
Hewitt landed massive changes and it's now back to <tree>foo</tree>.  The bug
this was marked a DUP of is indeed a global bug and affects the whole product.

*** This bug has been marked as a duplicate of 134889 ***

Comment 7

[Leston Buell]

To answer the first question in comment 5, sometimes an older bug gets duped to
a newer bug because the duplication is not immediately caught and more activity
has already begun on the newer bug. In this case the newer bug has already been
tagged mozilla1.0 and nsbeta1+ and many other bugs have been duped to it.

It's frustrating when the bug you were so quick to discover and report first
gets duped to something later. It's not fair, but to transfer the work already
done on the newer bug would be a senseless waste of time. If you report any
substantial number of bugs, some of them are bound to be duped to newer bugs.
Sorry. It's happened to all of us, and it doesn't mean that your bug report is
any less worthy  than the one to which it's duped.

Comment 8

[[e-mail] (gone - use [e-mail] instead)]

verified dup