Closed Bug 318239 Opened 19 years ago Closed 19 years ago

Bottom border of window much too wide

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 314768

People

(Reporter: brightpoint, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5 Much too large a border appears below status bar after installing v1.5. Reproducible: Always Steps to Reproduce: 1.Just launch browser... appears like clockwork 2. 3.
Does it go away if you start Firefox in safe mode (http://kb.mozillazine.org/Safe_Mode)?
It's exactly the same in safe mode.
*** Bug 318287 has been marked as a duplicate of this bug. ***
Then try deleting your install directory (C:\Program Files\Mozilla Firefox) and install Firefox once again.
*** This bug has been marked as a duplicate of 314674 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
(In reply to comment #4) > Then try deleting your install directory (C:\Program Files\Mozilla Firefox) and > install Firefox once again. > I already have installed Firefox in another directory and still the problem is (but I haven't deleted the first install directory, just made a fresh install elsewhere)
Joel or Marc, could you set the value javascript.options.showInConsole to true in about:config and post any errors in the JavaScript console (Tools -> JavaScript Console) mentioning chrome here?
Re: could you set the value javascript.options.showInConsole to true in about:config and post any errors in the JavaScript console (Tools -> JavaScript Console) mentioning chrome here? I'm not sure how to set the value javascript.options.showInConsole to true in about:config ??? I went to Tools ->JavaScript Console ...and I found many errors but I spotted nothing mentioning chrome. I also tried deleting my install directory and reinstalling v1.5 but I still have the same problem.
(In reply to comment #8) > I'm not sure how to set the value javascript.options.showInConsole to true > in about:config ??? > I went to Tools ->JavaScript Console ...and I found many errors but I spotted > nothing mentioning chrome. Type about:config into the address bar then type javascript.options.showInConsole into the 'Filter:' bar that appears. If javascript.options.showInConsole shows up under Preference Name, double-click it to set it to true. If it's not there, right-click anywhere in the white body portion of the window and select New -> Boolean. Enter javascript.options.showInConsole into the prompt and press Ok then once the next prompt comes up asking for the initial value, set it to true. You may have to restart for anything to show in the console.
ok, there were 2 new entries found in console. first: Error: no element found Source File: chrome://linky/content/main.xul Line: 1, Column: 1 Source Code: ^ Second: Warning: Failed to load overlay from chrome://linky/content/main.xul. Source File: chrome://browser/content/browser.xul Line: 0
Ah, looks like the Linky extension is to blame. Uninstalling it or updating it from here (http://gemal.dk/mozilla/linky.html) should fix the problem.
Status: RESOLVED → UNCONFIRMED
Resolution: DUPLICATE → ---
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → INVALID
Absolutly correct... Disabled Linky Extension....All is right with the world again! Thanks for hanging in there with me and finding the cause.
(In reply to comment #12) > Absolutly correct... Disabled Linky Extension....All is right with the world > again! > Thanks for hanging in there with me and finding the cause. > same thing for me ! thanks for solving the problem
*** Bug 318399 has been marked as a duplicate of this bug. ***
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
*** This bug has been marked as a duplicate of 314768 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago19 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.