Jump to content

Google Chrome NPAPI support

localzuk
 Share

Recommended Posts

localzuk

localzuk

Posted
Posted

So, Google are dropping NPAPI support from Chrome later this year, and they have now changed the default for it to be disabled.

 

What are other schools doing to deal with this? I know we use various plugins which use it still - Java, Silverlight etc...

Sagima

Sagima

Posted
Posted

Dealing with it by enabling it for now but if the services that use it haven't sorted themselves out by september we'll just use IE instead.

They announced the change was coming in 2013 I think and reminded people gain last november so surely most will be well on their way to having transitioned their products by now (although not MLS who when asked just told us to use IE until their html5 product is finished but that has no timescale yet)

TechMonkey

TechMonkey

Posted
Posted
If anyone's finance dept uses the Barclays BIB service, the login plugin breaks. I have a feeling they will not be updating it so it will be back to IE for them. I had just managed to convince everyone to transfer to Chrome as well!!
  • Thanks 1
  • 2 weeks later...
Arthur

Arthur

Posted
Posted (edited)
Sky Go uses Silverlight.... FOOLISHLY!

... and Sky aren't going to do anything about it! :rolleyes:

 

Sky has no plans to fix Chrome compatibility after Google's Silverlight shun

 

SKY HAS CONFIRMED that it has no plans to ditch Silverlight as a way of fixing Chrome compatibility in its Sky Go and Now TV services.

 

Streaming services including BT Sport and Now TV have gone to borksville as Google presses ahead with plans to kill off support for Microsoft Silverlight in its Chrome browser.

 

The Microsoft runtime depends on an ageing plug-in protocol called Netscape Plugin Application Programming Interface (NPAPI), for which Google is currently phasing out support in its browser.

 

However, Silverlight remains popular with broadcasters owing to its level of encryption and, although the news has been around since November, many are sticking to their guns instead of migrating to HTML5.

 

In a statement, Sky told The INQUIRER, "We continue to work with Google to find the best way to deliver our content on Google Chrome however there are no immediate plans to switch from the Silverlight player.

 

We recommend that a customer who previously used Chrome continues watching great Sky content using a different browser or via the range of other supported devices available."

 

Now TV has also been made available as a standalone app for Windows 8.1 and Windows 10.

 

Netflix has supported HTML5 EME since April 2013. Sky are showing an incredible lack of forethought!

Edited by Arthur
localzuk

localzuk

Posted
  • Author
Posted

I don't know if they are to be honest. The odd one out in all this is Google. No other browser is dropping NPAPI support. If people find they can't watch Sky Now on their browser, what are they more likely to do? Stop using Now TV or switch to Firefox? One they pay for, one is free and pretty much effortless.

 

Its Google that will lose out here.

dhicks

dhicks

Posted
Posted
The odd one out in all this is Google. No other browser is dropping NPAPI support.

 

If I understand correctly, Microsoft's Edge (Project Spartan) won't support NPAPI either.

Arthur

Arthur

Posted
Posted
No other browser is dropping NPAPI support.

Browsers on iOS, Android, Windows Phone etc. have either never had NPAPI support or have already dropped it. Likewise, neither Metro IE on Windows 8.x or Edge on Windows 10 have ever supported NPAPI (or ActiveX) plugins.

 

They are also dropping support of http at some point in the future.

Mozilla's plan is to deprecate non-secure HTTP, not stop supporting HTTP altogether.

 

https://blog.mozilla.org/security/2015/04/30/deprecating-non-secure-http/

 

After a robust discussion on our community mailing list, Mozilla is committing to focus new development efforts on the secure web, and start removing capabilities from the non-secure web. There are two broad elements of this plan:

 

  • Setting a date after which all new features will be available only to secure websites.
  • Gradually phasing out access to browser features for non-secure websites, especially features that pose risks to users’ security and privacy.

For the first of these steps, the community will need to agree on a date, and a definition for what features are considered “new”. For example, one definition of “new” could be “features that cannot be polyfilled”. That would allow things like CSS and other rendering features to still be used by insecure websites, since the page can draw effects on its own (e.g., using ). But it would still restrict qualitatively new features, such as access to new hardware capabilities.

 

The second element of the plan will need to be driven by trade-offs between security and web compatibility. Removing features from the non-secure web will likely cause some sites to break. So we will have to monitor the degree of breakage and balance it with the security benefit. We’re also already considering softer limitations that can be placed on features when used by non-secure sites. For example, Firefox already prevents persistent permissions for camera and microphone access when invoked from a non-secure website. There have also been some proposals to limit the scope of non-secure cookies.

 

It should be noted that this plan still allows for usage of the “http” URI scheme in legacy content. With HSTS and the upgrade-insecure-requests CSP attribute, the “http” scheme can be automatically translated to “https” by the browser, and thus run securely.

  • 2 months later...
_Rob_A_

_Rob_A_

Posted
Posted
In a scenario where we have Chromebooks and teachers use resources with Java or Flash, what can be done? Preventing upgrades to version 45 is only a temporary measue obvously,
CyberNerd

CyberNerd

Posted
Posted
In a scenario where we have Chromebooks and teachers use resources with Java or Flash, what can be done? Preventing upgrades to version 45 is only a temporary measue obvously,

 

Flash isn't an issue because pepperflash is built into chrome and it isn't an NPAPI plugin.

With Java et al we've used the same strategy as we did with OHP's: find another resource.

  • 1 month later...
Davit2005

Davit2005

Posted
Posted
Flash isn't an issue because pepperflash is built into chrome and it isn't an NPAPI plugin.

With Java et al we've used the same strategy as we did with OHP's: find another resource.

 

With Google we have stuck to Version 43 this year.

 

Unfortunately Java is a necessary :ballchain: evil for us for the foreseeable future, not only of Infrastructure Management (i.e. SAN switches, iLO's, Blade management, etc.) but also the majority of our Finance system.

 

Boy do I loathe web based management tools :censored:

localzuk

localzuk

Posted
  • Author
Posted
With Google we have stuck to Version 43 this year.

 

Unfortunately Java is a necessary :ballchain: evil for us for the foreseeable future, not only of Infrastructure Management (i.e. SAN switches, iLO's, Blade management, etc.) but also the majority of our Finance system.

 

Boy do I loathe web based management tools :censored:

 

Web based management tools are great, so long as the developers aren't clinging to the 90s. There is little need for plugins and addons now, with HTML5 and Javascript where they are.

 

We've moved to the latest version. If anyone really needs Java or the like, they can use IE11 which is also installed.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing


×
×
  • Create New...