Results 1 to 5 of 5

Thread: Pipelight no longer adds Silverlight to Chrome browser

  1. #1
    Join Date
    May 2012
    Location
    Planet Houston
    Posts
    64

    Default Pipelight no longer adds Silverlight to Chrome browser

    I am using opensuse 13.1.

    Lately, I've noticed that the Pipelight software no longer adds or is no longer able to add Silverlight to the Chrome browser. It is still added to Firefox, however. For a while, I have been using Chrome to view Netflix videos, but now that Silverlight is no longer added, I have switched back to Firefox when I want to watch Netflix. Thankfully, with the User Agent Overrider, Firefox does fine with Silverlight added through Pipelight.

    I also see that instead of Silverlight in Chrome, Chrome has added Widevine to its plugins. I tested a rental movie on Google Play, and I did not have to spoof the operating system. The movie played beautifully. So, the fact that I am using Linux did not matter in this case as long as the Widevine plugin was available.

    It is my understanding that Netflix may now be using Widevine in some instances. I tried using Netflix in Chrome with the Widevine plugin available, but Netflix would not play a video with or without the User Agent Switcher. Netflix kept wanting me to install Silverlight. So is it that Netflix does not use Widevine on PCs yet? If so, any reason why the Silverlight software can no longer seem to be added to Chrome?

    ~George

  2. #2
    Join Date
    Nov 2013
    Location
    Canadiana
    Posts
    461

    Default Re: Pipelight no longer adds Silverlight to Chrome browser

    Are you using chrome >= version 35? If so, NPAPI plugins are no longer supported so pipelight will not work.
    openSUSE Leap (42.1) 64 bit
    Plasma 5.4

  3. #3
    Join Date
    Jun 2014
    Location
    Italy
    Posts
    76

    Default Re: Pipelight no longer adds Silverlight to Chrome browser

    Quote Originally Posted by alanbortu View Post
    Are you using chrome >= version 35? If so, NPAPI plugins are no longer supported so pipelight will not work.
    I have the same problem, after updating Chrome most plugins don't work, among them JRE (Java Runtime Environment) which I really need. What's the proper way to get JRE working in newer versions of Chrome?

    Thanks.

  4. #4

    Default AW: Re: Pipelight no longer adds Silverlight to Chrome browser

    Quote Originally Posted by lorenzodes View Post
    I have the same problem, after updating Chrome most plugins don't work, among them JRE (Java Runtime Environment) which I really need. What's the proper way to get JRE working in newer versions of Chrome?
    Better open a new thread. This has absolutely nothing to do with pipelight or Silverlight, although the underlying issue might be the same (i.e. no more netscape plugins support in Chrome).

    Apparently there is _no_ solution for this at the moment though, I'm afraid: (other than downgrading Chrome to version 34)
    http://askubuntu.com/questions/47059...-google-chrome

  5. #5
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,273
    Blog Entries
    2

    Default Re: Pipelight no longer adds Silverlight to Chrome browser

    Quote Originally Posted by lorenzodes View Post
    I have the same problem, after updating Chrome most plugins don't work, among them JRE (Java Runtime Environment) which I really need. What's the proper way to get JRE working in newer versions of Chrome?

    Thanks.
    Actually, the reason for all the posts in this thread are related. You have a problem is that is all over the Internet regarding the latest/current version of Chrome, Google decided to fork from the official webkit project and announced about 8 mths ago give or take. You can google the responses... When this was announced there was consternation all around. For the first few months (and Chrome versions) there was little change as Google supposedly concentrated on refactoring and optimizing core functionality but with the latest Chrome is now starting to make changes that are implementing new APIs invalidating older plugins and how Java has been installed.

    Google claims that they were motivated to do this because in their opinion webkit had become too big and inefficient supporting so many browsers and indeed, Google claims to have significantly reduced substantial lines of code in re-factoring. IIRC Opera is following suit using Google's browser engine after initialy saying they would stay with webkit. That should leave Safari as the only major browser using webkit, plus all the little custom browser apps mostly included in mobile OS.

    For awhile, there will be some disruption and things may not work. I haven't followed up on this to verify which direction Canary and Chromium are going but assume they will use the new engine.

    TSU

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •