Zoeken in Support

Vermijd ondersteuningsscams. We zullen u nooit vragen een telefoonnummer te bellen, er een sms naar te sturen of persoonlijke gegevens te delen. Meld verdachte activiteit met de optie ‘Misbruik melden’.

Learn More

Deze conversatie is gearchiveerd. Stel een nieuwe vraag als u hulp nodig hebt.

Firefox no longer works with Amazon Prime video

  • 3 antwoorden
  • 1 heeft dit probleem
  • 2375 weergaven
  • Laatste antwoord van darweb2

more options

Firefox was just updated to version 91.0.2 (64 bit), and now the l;inks on Amazon Prime video no longer work. Many of the links take me to my Watchlist. I tried accessing the site using Chrome and Edge - no problems with those browsers. Firefox was working with Amazon last night, so this is something that happened with the recent update.

Firefox was just updated to version 91.0.2 (64 bit), and now the l;inks on Amazon Prime video no longer work. Many of the links take me to my Watchlist. I tried accessing the site using Chrome and Edge - no problems with those browsers. Firefox was working with Amazon last night, so this is something that happened with the recent update.

Gekozen oplossing

Thanks for the replies - did try clearing the cache, and the Web Console didn't have any relevant info. But checked it this morning and it seems the gremlins were busy overnight and fixed it.

Dit antwoord in context lezen 👍 0

Alle antwoorden (3)

more options

Make sure you are not blocking content.

Diagnose Firefox issues using Troubleshoot(Safe) Mode {web link}

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


https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-desktop


Many site issues can be caused by corrupt cookies or cache.

Warning ! ! This will log you out of sites you're logged in to. You may also lose any settings for that website.

more options

You can check the Web Console for media related messages.

more options

Gekozen oplossing

Thanks for the replies - did try clearing the cache, and the Web Console didn't have any relevant info. But checked it this morning and it seems the gremlins were busy overnight and fixed it.