Join the Mozilla’s Test Days event from Dec 2–8 to test the new Firefox address bar on Firefox Beta 134 and get a chance to win Mozilla swag vouchers! 🎁

Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

詳しく学ぶ

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

Clicking menus gives outline of drop down menu.

  • 7 件の返信
  • 6 人がこの問題に困っています
  • 8 回表示
  • 最後の返信者: rp108

more options

When I click a menu item, for example, Tools, I do not get a full drop down menu. It is just an outline of the menu. By moving the cursor, here and there, sometimes the full (correct) drop down menu will show up. There are no AddOns or PlugIns. 64 bit FF 55.0.3

Also, when FF shows that I have miss-spelled a word, such as in this box I am now typing in, if I Right Click to get suggestions, again, I just get an outline of a pop up spelling suggestions. Again, if I move the mouse around, the menu will usually fill in correctly, often a delay of 5-10 seconds.

When I click a menu item, for example, Tools, I do not get a full drop down menu. It is just an outline of the menu. By moving the cursor, here and there, sometimes the full (correct) drop down menu will show up. There are no AddOns or PlugIns. 64 bit FF 55.0.3 Also, when FF shows that I have miss-spelled a word, such as in this box I am now typing in, if I Right Click to get suggestions, again, I just get an outline of a pop up spelling suggestions. Again, if I move the mouse around, the menu will usually fill in correctly, often a delay of 5-10 seconds.

選ばれた解決策

This still sounds hardware acceleration related.

Are you really sure hardware acceleration is disabled?

You can check these prefs on the about:config page:

  • layers.acceleration.disabled = true
  • layers.acceleration.force-enabled = false

EDIT: If you use a custom theme then try to revert to the default theme.

  • "3-bar" menu button or Tools -> Add-ons -> Appearance

In Firefox Safe mode these changes are effective:

  • hardware acceleration is disabled (Options/Preferences -> Advanced -> General)
  • all extensions are disabled (about:addons)
  • default theme is used (no lightweight theme)
  • default toolbar layout is used
  • xulstore.json is ignored
  • userChrome.css and userContent.css are ignored (chrome folder in profile folder)
  • JavaScript JIT compilers are disabled
  • plugins are not affected
  • preferences are not affected
この回答をすべて読む 👍 2

すべての返信 (7)

more options

Start Firefox in Safe Mode {web link} by holding down the <Shift> (Mac=Options) key, and then starting Firefox.

A small dialog should appear. Click Start In Safe Mode (not Refresh). Is the problem still there?

more options

You can try to disable hardware acceleration in Firefox.

  • Options/Preferences -> General: Performance
    remove checkmark: [ ] "Use recommended performance settings"
    "Use hardware acceleration when available"

You need to close and restart Firefox after toggling this setting.

You can check if there is an update for your graphics display driver and check for hardware acceleration related issues.

more options

Folks, thanks for assistance.

Apologies, I forgot to mention that FF worked fine, BEFORE latest FF update. Problem only arose after update.

Hardware acceleration is off and always has been off.

Starting in SAFE MODE, does indeed fix the problem. But I don't understand, do I have to run in SAFE MODE forever more?

Also, I note that items like the Menu Bar are off by default in SAFE MODE, so, I add it back and other items.

But when I shut down and restart in SAFE MODE again, I have to add them all again.

Just as a test, after starting SAFE MODE, I shut down and tried the regular mode and the problem was still there.

So does the correct operation in SAFE MODE give some clue as to how to fix this and be able to run in regular mode so as to not not lose all my settings?

Many thanks to all for your attention in this matter.

Robert

more options

It could be the work of one of your add-ons. Type about:addons<enter> in the address bar to open your Add-ons Manager. Hot key; <Control> (Mac=<Command>) <Shift> A)

In the Add-ons Manager, on the left, select Extensions. Disable a few add-ons, then Restart Firefox.

Some added toolbar and anti-virus add-ons are known to cause Firefox issues. Disable All Of them.

If the problem continues, disable some more (restarting FF). Continue until the problem is gone. After, you know what group is causing the issue. Re-enable the last group ONE AT A TIME (restarting FF) until the problem returns.

Once you think you found the problem, disable that and re-enable all the others, then restart again. Let us know who the suspect is, detective.

more options

Hey Fred,

Thanks again. As I mentioned i the initial post, there are no add ons. I did indeed follow your commands with about:addons and it displays a simple notification box that "you don't have any add ons of this type"

Any other ideas my friend ?

Thanks again, Detective Robert

more options

選ばれた解決策

This still sounds hardware acceleration related.

Are you really sure hardware acceleration is disabled?

You can check these prefs on the about:config page:

  • layers.acceleration.disabled = true
  • layers.acceleration.force-enabled = false

EDIT: If you use a custom theme then try to revert to the default theme.

  • "3-bar" menu button or Tools -> Add-ons -> Appearance

In Firefox Safe mode these changes are effective:

  • hardware acceleration is disabled (Options/Preferences -> Advanced -> General)
  • all extensions are disabled (about:addons)
  • default theme is used (no lightweight theme)
  • default toolbar layout is used
  • xulstore.json is ignored
  • userChrome.css and userContent.css are ignored (chrome folder in profile folder)
  • JavaScript JIT compilers are disabled
  • plugins are not affected
  • preferences are not affected

この投稿は cor-el により に変更されました

more options

Cor-El an FredMcD,

THANK-YOU for sticking with me on this ! You guys are geniuses.

It was the; layers.acceleration.disabled that was the problem.

All is well now.

Best to both of you, rp108

-)