539314 - Seamonkey displays blank page instead of home page at load time

Status: RESOLVED WORKSFORME

(SeaMonkey :: Tabbed Browser, defect)

Description

[Ken Wilson]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100104 SeaMonkey/2.0.2
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100104 SeaMonkey/2.0.2

Loading an additional seamonkey iteration from the quicklaunch tray yields a blank page instead of the usual home page. This does not occur at initial load, but only on an additional load. It also does not seem to occur when loading a new tab.

Reproducible: Always

Steps to Reproduce:
1.Load seamonkey
2.Set home page
3.Load another iteration of Seamonkey from the Quicklaunch tray )beside the start button)



This is new since 2.0.2 installed an hour ago. This did not happen with 2.0.1 or earlier releases.

Comment 1

[:Hb]

It's assumed that you mean the Windows Quick Launch Bar and not the old "Quicklaunch" feature from SM1. Can't verify this on Windows XP. 

What is set in Preferences - Browser - Display on 
a) Browser Startup
b) New Window
c) New Tab

Comment 2

[Ken Wilson]

Yes, it is using the Windows Quick Launch Bar. This is under Vista Home Premium (all updates applied).

Preferences - Browser - Display on 
is set to a) Browser Startup

Comment 3

[Ken Wilson]

Resolved. After a subsequent (several days later) reboot of Vista the problem has vanished. Though it is not obvious how, the symptom must be O/S interaction related. Thanks.

Comment 4

[:Hb]

(In reply to comment #2)
> Preferences - Browser - Display on 
> is set to a) Browser Startup

Please not that the drop down changes only the meaning of the radio buttons below it. The what-should-happen settings for the three events Startup, New Window and New Tab are made with the appropriate radio buttons. This user interface is very uncommon and misleading. Typical Tabs are used in UI design for this. Because of this shortcoming I moved the bug to Tabbed Browser.

FIXED as resolution needs a code change which did not happen here. Possible options are INVALID for a bad bug report or WORKSFORME if the error can't be reproduced any more like this one.