Closed Bug 636937 Opened 13 years ago Closed 13 years ago

A cube shaped "dead" square after opening and closing the Preferences

Categories

(Firefox :: Settings UI, defect)

x86_64
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 641288

People

(Reporter: wmsecurity, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b13pre) Gecko/20110225 Firefox/4.0b13pre
Build Identifier: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:2.0b13pre) Gecko/20110225 Firefox/4.0b13pre

After the Preferences setting is opened and closed, there is a weird square that is covering the Forward, Next, Reload buttons and the first 2 tabs.

Reproducible: Always

Steps to Reproduce:
1. Launch Firefox
2. Open Firefox/Preferences
3. Close Preferences (OK or cancel)
Actual Results:  
Screenshot :
http://pix.am/zz3T.png


I tried with 3 different themes.

The default one, NNL, and one random from mozilla.org.
All the same.
Summary: A cude shaped "dead" square after opening and closing the Preferences → A cube shaped "dead" square after opening and closing the Preferences
Version: unspecified → Trunk
Can you still see the issue if you disable the hardware acceleration in Firefox
(Edit->Preferences->Advanced->General, uncheck "Use hardware acceleration when available") ?
I am experiencing this. It still occurs with "Use hardware acceleration when
available" unchecked.
I can confirm that the bug does not reproduce in safe mode.
Probably it is caused by one of the plugins/addons, need to research which one.
I am still experiencing this issue in safe mode.
Anton: The safemode disabled the hardware acceleration and addons.
Try disabling the addons and if that doesn't help disable the hardxware acceleration
Bug also occurs in safe mode
In my case the preference pane not only is left on screen, but is being opened on the left Side of the Firefox main window, halfway out of the screen.

When re-opening the preferences, the small sqaure "transforms" to the preference pane; so it semms the window associated with the pane is not closed at all, but only hidden...

See: http://img709.imageshack.us/img709/9811/bildschirmfoto20110525um.png
Did you try creating a new profile? I did experience this since yesterday, and creating a fresh profile solved it for me.
yes this worked for me too
The weird thing is that in the old profile I had »Ok« and »Cancel« Buttons and in the new profile I don't
(In reply to comment #13)
> The weird thing is that in the old profile I had »Ok« and »Cancel« Buttons
> and in the new profile I don't

with the old profile it opens in the browser window and with the new one in a separate window
its something in the prefs.js causing this and it should be easy to fix once the flag is identified.  Since switching to a new profile would be very inconvenient, I copied the prefs.js from the new file to my old one and that resolves it.
See bug 641288.

Marking this as a dupe of 641288 (even though this one was filed first) because 641288 diagnoses the problem and says how to fix it.  (Short answer: don't mess with pref browser.preferences.instantApply on OS X, and watch out for extensions that change it.)

Thanks Anton for reporting this.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → DUPLICATE
This bug was present when running TenFourFox 10.0.9 on a PPC Mac G4.  All of the reported behaviors occurred -- unable to select preference panes; the only way to dismiss the Preferences window was to use the Esc key, which left the blank square covering the back-forward arrows and the leftmost tab.  By deleting and adding back extensions, I was able to isolate the extension that was causing it on my Mac -- TRUSTe Privacy Plugin 2.0.  (This is not the same as TRUSTe Tracker Protection Beta 1.1.2c)  Disabling that extension got rid of the problem.
(In reply to mike bayer from comment #15)
> its something in the prefs.js causing this and it should be easy to fix once
> the flag is identified.  Since switching to a new profile would be very
> inconvenient, I copied the prefs.js from the new file to my old one and that
> resolves it.

Yes, this solved the problem for me too. I took the prefs.js from a backup of my profile, that I made before the problem started occurring. Thanks Mike for the tip.
You need to log in before you can comment on or make changes to this bug.