Closed Bug 324641 Opened 14 years ago Closed 14 years ago

Grey bar at bottom of options window/broken statusbar with new profile.

Categories

(Firefox :: General, defect, major)

x86
Windows 2000
defect
Not set
major

Tracking

()

VERIFIED FIXED

People

(Reporter: stevee, Assigned: peterv)

References

Details

(Keywords: regression)

Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20060125 Firefox/1.6a1 ID:2006012505
1. New Profile
2. Run firefox.
3. Tools > Options

Observe the grey bar at the bottom of the screen with red text in it.
This was not present on the 20060124 trunk build.
Note: You might have to click on some of the Option tabs to see the problem.
Also (with my proper profile) extensions are playing up.. ForecastFox has a "Formed Error" msg instead of the weather (worked fine yesterday trunk, still works fine on branch); sometimes on startup the grey bar appears at the bottom of the browser with strange red text in; etc.
Summary: Grey bar at bottom of options window. → Grey bar at bottom of options window with new profile.
I see this too and its pretty messed up. It seems to be random which tab in options causes the bar to appear and sometimes all just work perfectly. You can close the options and reopen and it will behave differently.

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060125 Firefox/1.6a1 ID:0000000000
This is almost certainly to do with the dynamic overlays used in the options. In the JavaScript Options extension (uses prefwindow with dynamic overlays) the same errors happen (and that extension hasn't changed for a while). Another extension I'm working on uses prefwindow without dynamic overlays and that has no problems.
Errors from javascript console when the error occurs:

Error: unclosed token
Source file: chrome://browser/content/preferences/privacy.xul
Line: 73, Column: 9
Source code:
        <tab label="&itemCache.label;"     helpTopic="prefs-cache"/>

Warning: Failed to load overlay from chrome://browser/content/preferences/privacy.xul.
Source file: chrome://browser/content/preferences/preferences.xul


I also saw this problem once when loading the main browser with similar errors.
Except for the red letters in the Options window, I had also 4 grey bars at the bottom, covering more than the half of my screen. They represented:

Toolbar Enhancements broken;
Quicknote broken;
Prefbuttons broken;
Sage broken.
Ria, you don't happen to have a build from between the 2 checkins in that regressionwindow, have you ?
A local back-out suggests that bug 323299 caused this.
Blocks: 323299
Summary: Grey bar at bottom of options window with new profile. → Grey bar at bottom of options window/broken statusbar with new profile.
(In reply to comment #7)
No, I have the same ones.
Happy to report: I have all my extensions working again!
Disabling and enabling brought them back to life.

Assignee: nobody → peterv
Also removing extensions.ini works BTW.
(In reply to comment #10)
> Also removing extensions.ini works BTW.

Didn't work for me.
My JSConsole is full with:
Error: this.docShell has no properties
Source File: chrome://global/content/bindings/browser.xml
Line: 0
Same problems (XML Parsing Error: unclosed CDATA section..., XML Parsing Error: unclosed token...) with options dialog in Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20060125 Mozilla Sunbird/0.3a1+. No problems with 20060124 build.
Flags: blocking1.9a1?
I see the XUL "parse error" right in front of me as Colorzilla is installed and using builds post:

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060124 Firefox/1.6a1 ID:2006012504
this should be fixed by the backout of bug 323299
please stop adding comments
See comment 15.
Status: NEW → RESOLVED
Closed: 14 years ago
Flags: blocking1.9a1?
Resolution: --- → FIXED
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20060125 Firefox/1.6a1 ID:2006012512

verified
Status: RESOLVED → VERIFIED
Could anyone reproduce this in a debug build?  It'd be nice to have an idea of what's wrong with the patch in bug 323299...
You need to log in before you can comment on or make changes to this bug.