Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Ce site disposera de fonctionnalités limitées pendant que nous effectuons des opérations de maintenance en vue de vous proposer un meilleur service. Si un article ne règle pas votre problème et que vous souhaitez poser une question, notre communauté d’assistance est prête à vous répondre via @FirefoxSupport sur Twitter, et /r/firefox sur Reddit.

Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

How do I force Netflix to use Silverlight?

  • 3 réponses
  • 7 ont ce problème
  • 1 vue
  • Dernière réponse par John99

more options

I was going to post this question, but then I figured out the answer, so now I'll post the question and the answer for anyone else who searches how to do this. This is for windows but may work on other OS idk.

My older computer runs netflix smoothly in silverlight, but choppy in html5.

Netflix detects that I run a browser which is supposed to have html5 DRM support, so it goes straight to using the html5 player. So I disable DRM in firefox, and set Widevine to never activate. But then when I try to watch a netflix video, instead of it using silverlight, which I have, it plays nothing and tells me to Enable DRM. That's pretty much a bug with their system or firefox, or just a poor design choice imo.

To fix it and force Netflix to use Silverlight, you just have to install a User Agent switcher and pretend to be a slightly older version of firefox (for example 40). Then Netflix will think your browser doesn't have html5 drm capability and it will use silverlight.

I was going to post this question, but then I figured out the answer, so now I'll post the question and the answer for anyone else who searches how to do this. This is for windows but may work on other OS idk. My older computer runs netflix smoothly in silverlight, but choppy in html5. Netflix detects that I run a browser which is supposed to have html5 DRM support, so it goes straight to using the html5 player. So I disable DRM in firefox, and set Widevine to never activate. But then when I try to watch a netflix video, instead of it using silverlight, which I have, it plays nothing and tells me to Enable DRM. That's pretty much a bug with their system or firefox, or just a poor design choice imo. To fix it and force Netflix to use Silverlight, you just have to install a User Agent switcher and pretend to be a slightly older version of firefox (for example 40). Then Netflix will think your browser doesn't have html5 drm capability and it will use silverlight.

Solution choisie

If silverlight was not being phased out, it would clearly be poor design to not fall back gracefully so the user can still get at the content. The phasing out is really the only excuse not to want to do that.

As it is, since silverlight performs more efficiently than the html5 player, this design choice (or oversight) is basically making a bunch of computers obsolete 5 months sooner than they need to be. (While a much much larger amount of computers are not affected lol.)

It's too bad that that html5 video is more demanding on hardware than silverlight and flash were.

Lire cette réponse dans son contexte 👍 0

Toutes les réponses (3)

more options

I did not know that happened. I would have presumed Netflix just no longer supports Browsers using Silverlight. I do not think it is a bug or poor design, you are just managing to exploit their loophole that allows support of legacy browsers.

At least by using a User Agent switcher to spoof a different version of Firefox you day to day browsing is done with a supported and safe Firefox version.

more options

Solution choisie

If silverlight was not being phased out, it would clearly be poor design to not fall back gracefully so the user can still get at the content. The phasing out is really the only excuse not to want to do that.

As it is, since silverlight performs more efficiently than the html5 player, this design choice (or oversight) is basically making a bunch of computers obsolete 5 months sooner than they need to be. (While a much much larger amount of computers are not affected lol.)

It's too bad that that html5 video is more demanding on hardware than silverlight and flash were.

more options

I will mark this solved. There is not anything more we will be able to do to fix this issue for you. Solved threads show up in internal and external searches so your post will be found and seen by more people.