Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 1202083, configs for funnelcake 50, 51, 52 - testing firstrun experience #2

Merged
merged 3 commits into from Sep 15, 2015
Merged

Bug 1202083, configs for funnelcake 50, 51, 52 - testing firstrun experience #2

merged 3 commits into from Sep 15, 2015

Conversation

FrancescoSTL
Copy link
Contributor

@nthomas-mozilla / @mixedpuppy r?

I think I did this all correctly. Let me know if there are any changes that need to be made!

@nthomas-mozilla
Copy link
Contributor

I would suggest not setting startup.homepage_override_url, that's for the update case and I'm pretty sure the update server will either suppress or override it anyway. Similarly, I'd leave out browser.startup.homepage because that's the default value.

For 51, why do you set startup.homepage_welcome_url="about:blank" instead of "" ? It seems like it'll open a blank page (next to about:home), which is suboptimal UX.

If you're not aware, you can test these configs by creating <install_directory>/distribution/ and dropping the distribution.ini in it. Then start firefox with the profile manager and create a new profile. Mac is a bit different, but that that should work for windows & linux.

@mixedpuppy
Copy link
Contributor

@nthomas in a recent partner config I found empty strings defined in distribution.ini would not override the default prefs. Using "about:blank" fixed that, it is specifically handled in nsBrowserContentHandler.js and results in no tab being opened, so long as there is a defined homepage. If both homepage and the welcome page are "about:blank" then the user will get a blank tab.

@nthomas-mozilla
Copy link
Contributor

mixedpuppy, sounds like you are better placed to review this code. I stand by the comments about startup.homepage_override_url - even if the update server doesn't intervene, the pref is undefined in vanilla builds and we don't want to show any particular content to these users.

@mixedpuppy
Copy link
Contributor

I was just responding on the about:blank override in my last comment, but I'll take a stab...

@FrancescoSTL
ISTM that both browser.startup.homepage and startup.homepage_override_url are unnecessary in these configs. I also wonder if startup.homepage_welcome_url in #52 shouldn't have "?f=52". Last, seems these configs are in the "old" directory. They instead need to be in a "desktop" directory to get built.

@FrancescoSTL
Copy link
Contributor Author

@mixedpuppy I've now removed the .homepage_override_url and .homepage_welcome_url settings, along with adding a query string to the firstrun url in funnelcake 52, and moved all three funnelcakes to the /desktop folder. Let me know if you see any other issues!

mixedpuppy added a commit that referenced this pull request Sep 15, 2015
Bug 1202083, configs for funnelcake 50, 51, 52 - testing firstrun experience
@mixedpuppy mixedpuppy merged commit 4d8279f into mozilla-partners:master Sep 15, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants