Firefox Updater triggers UAC prompt without warning




8 years ago
7 years ago


(Reporter: deuskane, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2011-1-30])



8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv: Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv: Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729)

If an update has been installed in the background, a UAC prompt will be triggered next time Firefox is launched, with no warning, or any indication that anything other than Firefox would be launched. As the UAC prompt is a full-screen notification that stops all other tasks, this is jarring and potentially confusing for users. The UAC window is not a replacement for an explanatory choice window, it is a security feature.

Reproducible: Always

Steps to Reproduce:
1.Install and run old version of Firefox
2.Wait for an update to be downloaded in the background
3.Close and re-open Firefox
Actual Results:  
A UAC prompt appears, halting all user actions, with only minimal explanation of what is happening.

Expected Results:  
A window should appear, with an explanation that an update is ready to be installed, and "cancel" and "install" buttons; the "install" button should have a UAC shield on it. Then, when the shielded button is clicked, a UAC prompt should be triggered. (specifically the section titled "User Experience Process Flow")
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode? If not, please close. These links can help you in your testing.

You can also try to reproduce in Firefox 4 Beta 8 or later, there are many improvements in the new version,
Whiteboard: [CLOSEME 2011-1-30]
No reply, INCOMPLETE. Please retest with Firefox 3.6.13 or later and a new profile ( If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.