296926 - After a upgrade operation, wep pages are shifted 20 cm from the left side of the browser window.

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Ozgur OZTURK]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322)
Build Identifier: 

Hello there,
I am using the version of 1.0.4 Mozilla Firefox. This is the great web browser 
and I want to thank you for this opportunity. But now, I have an interesting 
problem. I did upgrade this Firefox ten minutes ago and know web pages are 
shifted 15 cm from the left side of the browser. In addition, I see a message 
in red color, it seems like this : 
<menuitem label=&ff.menu.options.label;"accesskey=&ff.menu.options.accesskey;" 
default = "true" and so on (I do not see the remaining part)

I would like to send a printScreen of my firefox browser but it is not 
possible, why?


Thank you for your interest.
Ozgur OZTURK
Senior Software Engineer

Reproducible: Always

Steps to Reproduce:
1.I upgraded the software
2.Try to visit a web page
3.See the problem

Comment 1

[Ozgur OZTURK]

Attachment: This is the screenshot of the bug

Hello there,
I am using the version of 1.0.4 Mozilla Firefox. This is the great web browser 

and I want to thank you for this opportunity. But now, I have an interesting 
problem. I did upgrade this Firefox ten minutes ago and now, web pages are 
shifted 15 cm from the left side of the browser. In addition, I see a message 
in red color at the bottom of the browser window, it seems like this : 
<menuitem label=&ff.menu.options.label;"accesskey=&ff.menu.options.accesskey;" 

default = "true" and so on (I do not see the remaining part)

Comment 2

[Anders Conbere]

This is most likely an issue that is best handled in the mozillazine support
forums (that is an issue with a corupted file in your profile, a theme, or
extension).

mozillazine support forums can be found at:
http://forums.mozillazine.org/viewforum.php?f=38

If they can't solve this issue, come back here.

(This isn't to say that you might not have a real bug, only that I've seen
enough problems similar to this that my bet is that it's a support issue before
a browser bug, and that should be the first route taken.)

Thanks,
Anders