Skip to main content
Participant
December 26, 2016
Question

Problems with using FlashPlayer with Mozilla Firefox

  • December 26, 2016
  • 1 reply
  • 519 views

Problems with using FlashPlayer with Mozilla Firefox

I currently use a desk top PC and I have Flashplayer 24.0.0 and my default browser is Firefox 50.1.0

My problem is with using BBC iPlayer or ITV Hub.  With Flashplayer newly installed , I can get either BBC or ITV. However , neither BBC or ITV are available after my PC has been closed down and re-started. If I then re-install Flashplayer , BBC and ITV become available again.

If I change my browser to Google Chrome , I don’t have the same problem and both BBC and ITV are available all the time.

I prefer Firefox to Google Chrome but what is the compatability issue  between Firefox and Flashplayer. Is there a way round it ?

Regards

Terry Dennis

    This topic has been closed for replies.

    1 reply

    jeromiec83223024
    Inspiring
    January 12, 2017

    My guess is that this is related to DRM.  I'm not aware of a similar widespread problem affecting Firefox users and DRM content in a generic way.  It's more likely that there's something stale that's been cached.  The ecosystem for authenticating and validating your access to rights-managed content is very complex, involving a number of third-parties, and there are lots of possible failure points.

    I'm guessing that reinstalling Flash Player is just getting you a new DRM credential that's valid only for the session, which is odd, but explains why it works.  My first recommendation would be to clear your browser cache, and blow away all of Flash Player's stored data.  Alternatively you could launch a private browsing tab, and see if the problem works there.  Either of these should get you an instance that doesn't use any existing stored credentials.

    Go to Control Panel > Flash Player > Advanced > Delete All under Browser Data and settings, and also click Deauthorize This Computer.  This should blow away any stale credentials and DRM licenses that have been issued.

    At that point, hopefully the problem is solved, and it was just a stubborn cached file.  If not, something more nuanced is going on.


    Do you happen to be running any ad-blockers or anti-tracking plugins that might prevent JavaScript in this authorization ecosystem from working as written?  That might explain why your credentials work on the first try only...