Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

After updating FF to 37.0.2 the mouseover descriptions for Netflix movies no longer show/pop up. Works fine in other browsers.

  • 4 odpowiedzi
  • 2 osoby mają ten problem
  • 5 wyświetleń
  • Ostatnia odpowiedź od euthenia

more options

I have logged out of Netflix, cleared cookies, restarted FF, logged back in, and still cannot see the mouseover descriptions. Silverlight works just fine. I can stream content without any issues. But it is frustrating trying to browse without being able to view a video synopsis. I have tested with Chrome and IE (*ugh*), and I have no trouble getting the Netflix mouseover descriptions to popup.

I have logged out of Netflix, cleared cookies, restarted FF, logged back in, and still cannot see the mouseover descriptions. Silverlight works just fine. I can stream content without any issues. But it is frustrating trying to browse without being able to view a video synopsis. I have tested with Chrome and IE (*ugh*), and I have no trouble getting the Netflix mouseover descriptions to popup.

Wybrane rozwiązanie

Another common thing to try is clearing your Firefox cache, in case obsolete script or style files are causing the problem.

You can try Ctrl+Shift+r to reload that particular page (and all its components) fresh from the server.

If that doesn't help, you also can clear Firefox's cache completely using:

"3-bar" menu button (or Tools menu) > Options > Advanced

On the Network mini-tab > Cached Web Content : "Clear Now"

If you have a large hard drive, this might take a few minutes.


In case this is a new add-on related interaction, could you test in Firefox's Safe Mode? That's a standard diagnostic tool to deactivate extensions and some advanced features of Firefox. More info: Diagnose Firefox issues using Troubleshoot Mode.

If Firefox is not running: Hold down the Shift key when starting Firefox.

If Firefox is running: You can restart Firefox in Safe Mode using either:

  • "3-bar" menu button > "?" button > Restart with Add-ons Disabled
  • Help menu > Restart with Add-ons Disabled

and OK the restart.

Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).

Any improvement?


I no longer have a Netflix account, so I'm not sure whether I can test this out for myself.

Przeczytaj tę odpowiedź w całym kontekście 👍 1

Wszystkie odpowiedzi (4)

more options

Wybrane rozwiązanie

Another common thing to try is clearing your Firefox cache, in case obsolete script or style files are causing the problem.

You can try Ctrl+Shift+r to reload that particular page (and all its components) fresh from the server.

If that doesn't help, you also can clear Firefox's cache completely using:

"3-bar" menu button (or Tools menu) > Options > Advanced

On the Network mini-tab > Cached Web Content : "Clear Now"

If you have a large hard drive, this might take a few minutes.


In case this is a new add-on related interaction, could you test in Firefox's Safe Mode? That's a standard diagnostic tool to deactivate extensions and some advanced features of Firefox. More info: Diagnose Firefox issues using Troubleshoot Mode.

If Firefox is not running: Hold down the Shift key when starting Firefox.

If Firefox is running: You can restart Firefox in Safe Mode using either:

  • "3-bar" menu button > "?" button > Restart with Add-ons Disabled
  • Help menu > Restart with Add-ons Disabled

and OK the restart.

Both scenarios: A small dialog should appear. Click "Start in Safe Mode" (not Refresh).

Any improvement?


I no longer have a Netflix account, so I'm not sure whether I can test this out for myself.

more options

Many thanks, jscher2000!

I was able to track down the issue by troubleshooting my add-ons and extensions. Turns out that it is Greasemonkey, of all things. It was working fine until I updated to FF 37.0.2, so I'm assuming there is a conflict between the two that now renders Greasemonkey incompatible. That's a shame - I've used Greasemonkey for years and have come to rely on it to greatly enhance and customize my web experience.

I'm off to ask another question. Hopefully someone at Mozilla can release a fix for this.

more options

Greasemonkey mostly sits in the background... If you have userscripts which run on Netflix, you might need to check with the script authors on whether they need an update.

more options

I'll do that. Thanks again!