Closed
Bug 404737
Opened 17 years ago
Closed 14 years ago
No master password prompt (for proxy authentication info) for addons update checker while upgrading a Firefox 2 profile to Firefox 3 beta1
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: nirbheek.chauhan, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.1.9) Gecko/20071121 Firefox/2.0.0.9
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.1.9) Gecko/20071121 Firefox/2.0.0.9
While starting Firefox 3 with a Firefox 2 profile with N addons (upgrading ie), at first startup, when the existing extensions are checked for compatibility and updates, no master password dialog is prompted, and N empty proxy authentication boxes are prompted instead; where N is the no. of addons, and there is no master password box anywhere among the N prompts.
This is a regression from Firefox 2, since I distinctly remember that after the upgrade to 2.0.0.9, the compatibility checker prompted me for one master password box, followed by one filled-up proxy authentication box.
Reproducible: Always
Steps to Reproduce:
1. Backup existing ff2 profile and start ff3b1 with the firefox 2 profile
2. Get prompted for N empty proxy authentication boxes, where N = no. of addons
3. "..."
Actual Results:
Getting literally overwhelmed by the no. of proxy auth boxes to be filled up which pop up, and no master password box among any of them
Expected Results:
Just one master password prompt which will subsequently prompt with one filled-in proxy auth box.
Comment 1•17 years ago
|
||
Not sure what's happening here, is EM running at this point without a profile, so PSM and the password manager don't have data to work with? But then how does it know to use a proxy?
Comment 2•17 years ago
|
||
(In reply to comment #1)
> Not sure what's happening here, is EM running at this point without a profile,
> so PSM and the password manager don't have data to work with? But then how does
> it know to use a proxy?
I don't think that is the problem. I believe it is to do with how an XMLHttpRequest handles authentication.
Reporter | ||
Comment 3•17 years ago
|
||
I just got back to my machine after a vacation, and I tested the upgrade from Firefox 3.0b1 to 3.0b2. There seems to have been an improvement in the addon manager, since this time instead of popping N proxy authentication prompts boxes, the addon compatibility checker popped up only one proxy authentication prompt.
So, the problem is partially fixed (in that it's far less annoying now), but the addon compatibility checker still doesn't prompt for the master password, and just prompts an empty proxy authentication dialog.
Comment 4•17 years ago
|
||
This problem is still reproducible for me. I just upgraded to Firefox 3b2, and when opening the browse, a proxy authentication dialog was opened for each extension that I have installed for Firefox 2.0.0.11. I can reproduce the problem every time by closing and re-opening Firefox.
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9b2) Gecko/2007121016 Firefox/3.0b2
Reporter | ||
Comment 5•17 years ago
|
||
(In reply to comment #4)
> This problem is still reproducible for me. I just upgraded to Firefox 3b2, and
> when opening the browse, a proxy authentication dialog was opened for each
> extension that I have installed for Firefox 2.0.0.11. I can reproduce the
> problem every time by closing and re-opening Firefox.
>
Ah, I was talking about the upgrade from ff 3.0b1 to ff3.0b2; not from ff 2.0.0.11 to ff 3.0b2.
Comment 6•17 years ago
|
||
Actually, I'm able to reproduce it in either case.
Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
Comment 7•14 years ago
|
||
Nirbheek, do you still have this issue with Firefox 4?
Reporter | ||
Comment 8•14 years ago
|
||
I'm not entirely sure since I mostly don't use a proxy, but I believe the problem is gone now. The addons update checker prompts for the master password if required for proxy authentication.
Comment 9•14 years ago
|
||
Thanks for your quick reply. I will mark this bug as WFM now, but feel free to reopen if the issue should reappear.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•