Initial opening of Mozilla from e-mail link.



13 years ago
11 years ago


(Reporter: JLR, Unassigned)


1.8 Branch
Windows XP

Firefox Tracking Flags

(Not tracked)




13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050217
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8b) Gecko/20050217

Help shows: Mozilla 1.8b

I think the is a single click/double click problem from the e-mail client.
MS Outhouse Express 6, 5.00.0000.0000

When I open the Internet browser (Mozilla) from the e-mail client, sometimes not
always I get two browsers opening at once and when they finally get through
opening and presenting it's opening page (BTW: not always what the e-mail link
was) not one but two windows open. The first is normal size, and the second is
full screen size, NOT full screen but opened so there are no margins around the
window. When this happens the first thing I notice is that the bookmarks are
empty, there are probably other things but that's the first. I close the windows
and try the action again and it works properly, the link in the e-mail opens in
the Mozilla window. 

Reproducible: Sometimes

Steps to Reproduce:
On initial boot of WindowsXP Pro
1. Open e-mail client - OE6.
2. browse e-mail
3. click on some link in the e-mail to open the Mozilla browser to that URL.

Actual Results:  
Not one but two windows open.
Second window, underneath the primary window open totally blank and full screen.

Expected Results:  
Only one window should open with the appropriate ULR from the e-mail link.

Again I think this is a single click / double click issue.
Possibly, but I'm guessing something related to user setup and default because
the user selection screen sometimes opens also.

Comment 1

13 years ago
Could you test in the latest builds and see if you're still seeing this?
Assignee: p_ch → general
Component: Bookmarks → General
QA Contact: bookmarks → general
Version: unspecified → 1.8 Branch

Comment 2

13 years ago
Reporter, if you cannot reproduce the problem with a current SeaMonkey build
(1.8b is ancient), then please resolve this bug as invalid.

Comment 3

11 years ago
Since the reporter has not responded to comment #1 in over 2 years, I am resolving this bug as incomplete.  The reporter can feel free to reopen it and supply the missing information if the bug is still present in a recent SeaMonkey build.
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.