Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Mozilla Destek’te Ara

Destek dolandırıcılığından kaçının. Mozilla sizden asla bir telefon numarasını aramanızı, mesaj göndermenizi veya kişisel bilgilerinizi paylaşmanızı istemez. Şüpheli durumları “Kötüye kullanım bildir” seçeneğini kullanarak bildirebilirsiniz.

Learn More

Bu başlık arşivlendi. Yardıma ihtiyacınız varsa lütfen yeni bir soru sorun.

Closing the preferences window leaves a 1 inch square gray box in the upper left portion of the main window directly below the Apple menu bar.

  • 1 yanıt
  • 82 kişi bu sorunu yaşıyor
  • 5 gösterim
  • Son yanıtı yazan: iwilcox

dadadean
dadadean
more options

MacBookPro2,2 Intel Core 2 Duo 2.33 GH OS X 10.6.7

The box covers the Firefox Close, Minimize and Maximize buttons, the page forward and page back and the left of the Bookmarks Toolbar. I can move the Firefox window down and to the right and the gray box floats above, unmoved. Closing Firefox removes the gray box. I can work around it, but it doesn't seem right to have to restart the application anytime I make a change to the preferences.

MacBookPro2,2 Intel Core 2 Duo 2.33 GH OS X 10.6.7 The box covers the Firefox Close, Minimize and Maximize buttons, the page forward and page back and the left of the Bookmarks Toolbar. I can move the Firefox window down and to the right and the gray box floats above, unmoved. Closing Firefox removes the gray box. I can work around it, but it doesn't seem right to have to restart the application anytime I make a change to the preferences.

Tüm Yanıtlar (1)

iwilcox
iwilcox
more options

This seems to be bug 641288, and one workaround seems to be to visit about:config and change browser.preferences.instantApply to true. While it looks like a Firefox bug at its core, a commenter there said an unnecessary practice by some add-on authors probably revealed it; that practice is now flagged in the add-on validator so authors should spot it and fix it eventually. I'm not sure what the policy is on accepting non-validating add-ons at addons.mozilla.org, but as broken ones are making it in and causing this problem for some, I'd guess it's still possible. I'd speculate that until the underlying Firefox bug is fixed, updating such add-ons will revert the workaround.