Closed Bug 923929 Opened 11 years ago Closed 11 years ago

Defect - Nightly not taking all defaults

Categories

(Firefox for Metro Graveyard :: Install/Update, defect)

x86_64
Windows 8
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: ally, Unassigned)

Details

:kar paid me a visit because metrofx won't start. We went through the usual flow, clicked 'make Nightly my default browser" ..and metrofx would not launch.  I checked the control panel, and Nightly only took 6 of the defaults, so did not start in metro mode.

I gave it all of the defaults and it fixed the issues.

There is a clear user expectation (as expressed by the other Product Manager working on a tablet product) that setting Nightly as default browser should take all the defaults.
It sounds like there may be an issue buried here but it is not what it looks like on the surface. (Multi install related? Possibly already posted, going direct to control panel and not through the browser maybe)

The only default that matters for allowing us into Metro is HTTP (which also gives HTTPS for free).

For flyouts like we show on startup of firefox, or when we first install, those can only take one default. And we go for HTTP at that point. So that part of it is by design. 

Also after installing you may notice we have a couple of extra defaults. Those are because they are deemed less important by Microsoft and are not protected by a cryptographic hash, so we grab them for free.
Summary: Nightly not taking all defaults → Defect - Nightly not taking all defaults
Whiteboard: [triage] feature=defect c=tbd u=tbd p=0
I've only ever seen this when I've had my Nightlies mixed up, i.e. an official nightly vs. my local build. Its not clear at that point which Nightly you are setting as default and which your shortcuts are trying to launch for you.
Karen, I hope your metro browser is now working smoothly. :) 

:bbondy inquires in comment 1 if you had multiple firefoxes installed on your win8? Did you have a local build anywhere?

:bbondy, when I was troubleshooting her issue, we used the in-browser prompt, and that didn't work, so I then went through the control panel and that worked.
Flags: needinfo?(krudnitski)
Thinking through my scenario and the above comments, I think I know what's happened.

I had a Yoga first, and I took it off a UX guy who had a UX nightly build on the machine. I had downloaded the correct build from our website (nightly) and I couldn't ever Firefox metro run, even after making it my default everywhere. Any time I would press on a Skype (metro) link, the browser would try to start up and fail, so I always had to copy & paste the link into my Firefox classic desktop browser.

I then got a brand new machine (X1 carbon touch) which is what Ally saw. I had no local build, but did have a Firefox release build on there. I had downloaded nightly but I couldn't really 'find' it anywhere, so something got messed up. But Ally was able to finally get it working (which is great). But I think this is something we'll have to watch out for specifically in the 'download for new user' flow.

Luckily enough, I should get a new machine shortly while I'm in Toronto soon and I can take meticulous notes about what I would do as a typical user (and see how that works) and quiz my colleagues to do the same.
Flags: needinfo?(krudnitski)
Whiteboard: [triage] feature=defect c=tbd u=tbd p=0 → [block28] feature=defect c=tbd u=tbd p=0
Blocks: 935467
Whiteboard: [block28] feature=defect c=tbd u=tbd p=0 → [release28] feature=defect c=tbd u=tbd p=0
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → WORKSFORME
No longer blocks: metrov1backlog, 935467
Whiteboard: [release28] feature=defect c=tbd u=tbd p=0
You need to log in before you can comment on or make changes to this bug.