Closed Bug 796860 Opened 13 years ago Closed 2 years ago

Messed up branding when setting browser as default with multiple installs

Categories

(Firefox :: Installer, defect, P3)

x86_64
Windows 8
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox18 - wontfix

People

(Reporter: sbadau, Unassigned)

References

Details

(Whiteboard: [win8])

Attachments

(1 file)

Mozilla/5.0 (Windows NT 6.2; WOW64; rv:18.0) Gecko/18.0 Firefox/18.0 I stumbled upon this issue while verifying Bug 790667. I had several Firefox version installed in different locations. Setting them as default one after another breaks the branding. Please see the attached screenshot for more details. Reproducible: always Steps to reproduce: 1. Install the latest Aurora in a custom location (e.g Desktop) 2. Install the latest Nightly in a standard location (e.g C:\Program Files (x86)\Nightly) 3. Launch the latest Aurora and set it as a default browser from: Tools menu -> Options -> Advanced -> Make Aurora the default Browser. 4. In the Set Default Programs window select Aurora from the Programs category and Set this program as default. 5. Launch the latest Nightly and set it as default (from: Tools menu -> Options -> Advanced -> Make Nightly the default Browser.) 6. The Set Default Programs window opens - observe the Nightly branding in the Programs category Expected results: The latest Nightly branding is properly displayed. Actual results: The latest Nightly has the Aurora branding.
Whiteboard: [win8]
Jim: I'm thinking maybe cache or something?
Yeah, I run into this a lot when switching between different builds on Win8. I sense there's probably some new registration entries that need to get reset when we set as default (like the cached splash and icon images for metro). Might also be bugs in Windows control panel. The preview release had a real problem with refreshing info in the default programs interface.
There's still that shell function we're supposed to call at the end of installation as well. But they only really say to call that for Metro browsers, this is a general windows 8 problem. So not sure. Simona you can't reproduce this on Win7 right?
(In reply to Brian R. Bondy [:bbondy] from comment #3) > There's still that shell function we're supposed to call at the end of > installation as well. But they only really say to call that for Metro > browsers, this is a general windows 8 problem. So not sure. > > Simona you can't reproduce this on Win7 right? Yup, you're right, I can't reproduce this on Windows 7.
Brian, passing on this to you feel free to reassign if needed
Assignee: nobody → netzen
I think that multiple installs of different Firefox versions is more of a power user thing. Also it only effects win8. Does it need tracking? I don't question your judgement, I just want to provide the information I have :)
Rob, I think the best way to fix this is to change FirefoxURL to <brand>URL etc. Are you opposed to this? We could delete a bunch of values before showing the default selection Windows UI, but the problem with that is if a different Firefox brand is already the default, we'd mess it up if the user doesn't make a default selection after clicking on the set default browser and the OS "select your default browser" pops up.
I was hoping this wouldn't be a high priority nor tracked bug as per Comment 6.
I don't think this bug is significant enough to be tracked and that we shouldn't try to rush a fix in for this.
Summary: Messed up branding when setting browser as default → Messed up branding when setting browser as default with multiple installs
Since I didn't receive a replay to the "10/18 - Bugs tracked for Firefox 17/18" email I am resetting tracking to ? to have this bug reevaluated per comment #6, comment #8, and comment #9
Assignee: netzen → nobody
See Also: → 961003
Component: Shell Integration → Installer
Priority: -- → P3
Severity: normal → S3

I'm going to close this bug as WFM because Firefox Nightly and Firefox Developer edition can no longer be installed on Windows 8 due to discontinuation. However, if we encounter a similar issue with different steps or scenarios, we can reopen it.

Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: