511239 - Private Browsing Default Zoom Level is Greater than 100%

Status: VERIFIED DUPLICATE of bug 487656

(Firefox :: Private Browsing, defect)

Description

[Nathan Taylor]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729)

I've noticed that in both Windows XP and Windows Vista running Firefox in Private Browsing mode causes the browser to load with a greater-than-default zoom level. This is bothersome considering custom zoom levels are not preserved while in Private Browsing and thus I am forced to decrease the zoom of pages I visit while in Private Browsing mode.

Reproducible: Always

Steps to Reproduce:
1.Enter Private Browsing
2.View a website
Actual Results:  
The page was zoomed in to a level greater than 100%.

Expected Results:  
The page is zoomed into the default level.

Comment 1

[Nochum Sossonko [:Natch]]

Can you try starting Firefox in regular mode, going to the webpage you've encountered this issue on and resetting the zoom level, then re-enter private browsing mode and see if it works?

Otherwise I'd suggest trying this on a new profile, http://support.mozilla.com/en-US/kb/Basic+Troubleshooting#Make_a_new_profile .

Comment 2

[Nathan Taylor]

I tried the first suggestion and that made no difference. When I create a new profile and run private browsing I no longer experience the zoom issue. Interestingly, I've noticed this issue on two entirely separate machines.

One thing that puzzled me was that when I go to private browsing on the default profile I see a (slightly) different display than I do with the new profile I created:

http://img5.imageshack.us/img5/3651/differenterrors.jpg

Obviously these are the same message but the top one appears on my current profile and the bottom one for the new profile.

Comment 3

[Nochum Sossonko [:Natch]]

That's weird, but that also says that you have a bad profile on your system. Did you use that profile with earlier beta builds of 3.5 or 3.1?

Comment 4

[Nathan Taylor]

I did use a beta build on my other client, not this one though. Either way, guess I'll just create a new profile to handle this problem.

Comment 5

[(no longer active)]

Nathan, this is indeed a valid bug which has already been filed and fixed.  The fix will hopefully be ported to a dot release on the 3.5 branch (3.5.3 or 3.5.4) soon.