Bug 64917 - Mozilla opens a browser window with a blank page
Summary: Mozilla opens a browser window with a blank page
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: mozilla
Version: 7.3
Hardware: i686
OS: Linux
medium
low
Target Milestone: ---
Assignee: Christopher Blizzard
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-05-14 14:51 UTC by Ted Clark
Modified: 2007-04-18 16:42 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-05-14 14:51:10 UTC
Embargoed:


Attachments (Terms of Use)

Description Ted Clark 2002-05-14 14:51:04 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020408

Description of problem:
Mozilla will open a browser window with a blank page even if 'home page on
startup' is selected in preferences if there is already an instance of Mozilla
running.  This is correct behavior if the previous instance of Mozilla is a
browser window, but it will also exhibit this behavior if the previous instance
is a Mozilla Mail window.  The determination as to whether a home page should be
loaded or not should be based on the number of browser windows open, not on the
number of Mozilla instances already running.

AFAIK this is a design issue, not an implementation bug.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Close all Mozilla browser windows.
2. Open Mozilla Mail.
3. Select Edit->Preferences->Navigator from the menubar, enter a URL for  a
homepage, and select the home page on startup radio button.

4. Open a Mozilla browser window.

Actual Results:  Mozilla will open a browser window with a blank page.

Expected Results:  Mozilla should open a browser window and display a home page,
since this is the first browser window opened.

Additional info:

mozilla-0.9.9-7

Comment 1 Christopher Blizzard 2002-08-29 22:38:03 UTC
I think that this is because of the way that xremote works.  Please report it
upstream to get it fixed, it's probably not going to get fixed here.


Note You need to log in before you can comment on or make changes to this bug.