Closed
Bug 350683
Opened 18 years ago
Closed 18 years ago
After system restore, Firefox window suddenly has additional "gray space"
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: baranxi, Unassigned)
Details
Attachments
(1 file)
143.07 KB,
image/jpeg
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6 After my computer went extremely buggy (again, some more), I thought it was time for another system restore. I did it, no problems during the process, but since then, when I start Firefox, it has an additional grey space below the status bar. It stays when resizing the window, and whereas it is a cosmetic problem, it seriously hampers the readability of any site, and the only workaround is switching to another browser. Reproducible: Couldn't Reproduce Steps to Reproduce: 1. Windows system restore Actual Results: The superfluous space appeared. Expected Results: I expected no change with Firefox.
Comment 2•18 years ago
|
||
Please retest with disabled extensions or in Firefox's safe-mode. If a bad extension is not the cause you could try a clean reinstall. First delete the installation folder (by default in Program Files). http://kb.mozillazine.org/Safe_Mode_(Firefox)
(In reply to comment #2) > Please retest with disabled extensions or in Firefox's safe-mode. > If a bad extension is not the cause you could try a clean reinstall. > First delete the installation folder (by default in Program Files). > http://kb.mozillazine.org/Safe_Mode_(Firefox) > Worked like a charm, the "grey space" is gone. Thanks a lot!
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Updated•18 years ago
|
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Updated•18 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago → 18 years ago
Resolution: --- → WORKSFORME
Comment 4•18 years ago
|
||
*** Bug 360017 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•