Closed Bug 140155 Opened 22 years ago Closed 22 years ago

can't select bottom message

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Linux
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 134889

People

(Reporter: davidmaxwaterman, Assigned: sspitzer)

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; MSIE5.5; Windows 98;)
BuildID:    2002042510

In the message list pane, you can't scroll down to make the bottom most email
visible. I think it is only revently arrived emails which suffer from this. You
can't select it with the mouse either, since it is mostly off the bottom of the
window.

Reproducible: Always
Steps to Reproduce:
1.get new email
2.try to select or scroll down
3.

Actual Results:  nothing - you have to select a message above the bottom message
and hit 'next message'

Expected Results:  should scroll to make the bottom message visible and selectable.
This sounds like remnants of bug 134889... I tried with apr25 trunk build, linux
rh6.2 and if the bottom message header is partially obscured in the thread pane
we now scroll the message upward.  If selecting in sequence at the end of the
thread pane, it creates a somewhat weird effect, but you can indeed select and
read the last message.
laurel@netscape.com  wrote :
> This sounds like remnants of bug 134889... I tried with apr25 trunk build, linux
> rh6.2 and if the bottom message header is partially obscured in the thread pane
> we now scroll the message upward.  If selecting in sequence at the end of the
> thread pane, it creates a somewhat weird effect, but you can indeed select and
> read the last message.

I don't think you're looking at the same problem. I can also scroll, read and
select the bottom message, but not if it has just been received.

I have 'check for new messages every 1 minute' set and it will add a message to
the list when there's one to download. It is this message that you cannot scroll
to see....(although...)

Damn. Just tried it again by sending myself a message and it worked fine. It
must be something more complicated than I thought. I'll add when I figure out
what it depends on...

Max.

*** This bug has been marked as a duplicate of 134899 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
reopening
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---

*** This bug has been marked as a duplicate of 134889 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago22 years ago
Resolution: --- → DUPLICATE
verified dup
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.