[MacOSX] Login prompt for popmail appears in front of browser and not messenger

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
RESOLVED EXPIRED
16 years ago
8 years ago

People

(Reporter: grylchan, Unassigned)

Tracking

Trunk
PowerPC
Mac OS X

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
This is only on OS X. Didn't see on os 9.

Using commercial trunk 2002091008 on MAC 10.1.5

If you create a new profile, create a new pop mail acnt,
don't login, quit, restart browser, then start mail,
you will see the login prompt for pop account (the sheet
as they are called on OS X) drop down from browser window
instead of messenger.

I also saw this problem with webmail or aol mail also.
But in these cases you need to create pop mail then webmail or aol
and you will see prompt for webmail or aol login appear in front
of the browser. See bugscape bug 19859.

Steps:
1.create new profile
2.start mail
3.create a pop mail account.
4.After done creating, while Account Settings window is open,
  verify the pref 'check new mail at startup is checked'.
5.Click ok, then quit
6.Restart the browser
7.Start mail

result: pop mail login screen drops down in front of the browser
expected: to drop down in front of messenger

What's weird is that if I try exact same steps but with a imap
acnt instead of pop, it works fine. Then when you add
aol/webmail to commercial it really gets weirded out.

Updated

16 years ago
QA Contact: olgam → esther
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: esther → message-display
Summary: Mac OS X only:login prompt for popmail appears in front of browser and not messenger → [MacOSX] Login prompt for popmail appears in front of browser and not messenger

Comment 1

9 years ago
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
Status: NEW → UNCONFIRMED

Comment 2

8 years ago
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
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.