I don't know if there will be non Metro builds in the future, but this can explain why some people can't use the metro browser on Nightly. This would also effect any user who wanted to keep older installs on their computer if installed after the metro browser. Even on Release channel. Steps to reproduce: 1. Install Metro enabled Nightly build to the default install location. 2. Open the browser and set it as the default. 3. Install a Nightly build from any channel other than release, beta, and aurora that does NOT have Metro to an alternate location 4. Try to start the Metro browser in the start screen. Actual results: The Metro tile disappears even though the new build was not set as the default. The start menu shortcut gets updated to the new install location that does not support Metro. Expected results: The Metro tile does not disappear and stays set to the default browser. The start menu shortcut should not be created or should be created with an alternate name.
I think this is unlikely to hit significant numbers of users in the wild so we probably don't need this for v1.
Does this still happen?
Brian, Unfortunately there isn't any Nightly builds available that don't include Firefox Metro. The ones that don't have Firefox Metro are only zip files making the test invalid as this needs an installable. Could you please ask me to re-check this when Firefox Metro gets pushed into the Aurora channel? This way I can check with both Firefox Metro and none Firefox Metro Aurora builds.
Ah, good idea! Will do.
Sounds good, I will add this as a lower priority bug on my to-do list. I will keep you updated Brian.
OS: Windows 8 Metro → Windows 8.1
Mass close of bugs in obsolete product https://bugzilla.mozilla.org/show_bug.cgi?id=1350354
Status: NEW → RESOLVED
Last Resolved: 2 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.