Closed Bug 24916 Opened 25 years ago Closed 25 years ago

Need startup URL for browser

Categories

(SeaMonkey :: UI Design, defect, P2)

defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jevering, Assigned: sspitzer)

Details

(Whiteboard: [PDT+] checking in 2/16)

For beta, we need the browser to start up with a specific URL for the first time
launch.  Subsequent launches should start up to the regular netcenter home
page.  This is similar to how 4.x would start up on the registration page the
very first time only.
Target Milestone: M14
looks like 4.x uses browser.startup.agreed_to_license,
is this what you want?  Will Mozilla need to have a license
agreement too?

Or we can make a pref like "browser.startup.first-time" that
really will only come up once.

jevering says this is a first-time URL, not
a license thing.
yep, and we have to do it for beta.
Keywords: beta1
Priority: P3 → P2
This start-up page will be hosted at Netcenter and will introduce users to My 
Sidebar and the features of our software.  

Focus groups last year told us that it is vital that users immediately 
understand that My Sidebar is their's to do what they want, not Netcenter's to 
push to them what Netcenter wants.  This start-up page will help us do this to 
guarantee a successful first impression of My Sidebar.
Putting on PDT+ radar for beta1.
Whiteboard: [PDT+]
Summary: [Beta1] Need startup URL for browser → Need startup URL for browser
Temporarily use the following URL (will change to a Netcenter hosted URL or 
local file later)

http://client/seamonkey/navigator/whatsnew1.gif

Also note that this page will showcase what you can do with all those standards 
we support in Gecko - will be really cool.
john, can we get an external version of this?
I can push to mozilla.org if that's Ok.
adding sspitzer.
here's what we'll do:

in all.js we'll set the following prefs:

"startup.firsttime.page" to "http://www.mozilla.org/welcome.html"
"startup.firsttime" to "true"

and in the code, we'll do:

if ("startup.firsttime") {
	load "startup.firsttime.page";
	"startup.firsttime" = false;
}

for the commercial product, you just override those prefs in all-ns.js

I'm working on figuring out the right place for this code now.
correction, I'll use the 4.x prefs for this instead.

"browser.startup.homepage_override"
"startup.homepage_override_url"

in 4.x, "startup.homepage_override_url" was
"http://home.netscape.com/home/first.html"
testing a fix for this now.
sorry, the bool pref is "browser.startup.homepage_override"

and, we'll probably need to use "browser.startup.homepage_override.1" because if
the user migrated from 4.x, "browser.startup.homepage_override" would have
already been sent to false.

so, we'll use "browser.startup.homepage_override.1" or something like that in
5.0
fix in hand, will get reviewed today.
stealing this bug from mcafee
Assignee: mcafee → sspitzer
for mozilla, I'm using http://www.mozilla.org/mozorg.html for the first time
page

for ns, I'm using "http://home.netscape.com/home/first.html"

after I check in, you can change those in config.js (for mozilla) and
config-ns.js (for ns)
Status: NEW → ASSIGNED
updating summary to reflect that I'll be landing sometime today.
Whiteboard: [PDT+] → [PDT+] checking in 2/16
code reviewed by alecf, seeking checkin approval now.
fix checked in.  a=jevering.

two things left:

get a new first time page for the commercial build
get a new first time page for the mozilla build
update the prefs to point to those new pages.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
hmm interesting. Right now the release notes are used as the default
home page for milestone builds. I think its more useful to use that as
the firstime startup page. If we use that as the firsttime startup page
then the default page could change to mozilla.org? Or do we always want
to send people to the release notes?

CCing christine and blizzard for their opinions.
remember, this is something they see the first time they start up with a new
profile in 5.0

so if you go from milestone a to milestone b, you won't see that page.

this is more of a "welcome to 5.0, it's you first time!" page
verified, looks like we are directed to 
http://home.netscape.com/home/su_setup.html where hopefully we'll get something 
that doesn't say welcome to communicator eventually :-)

second time you run you're back to your good old home page
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.