You may choose to change Chrome's auto-update behavior to ensure that Chrome does not get updated automatically and your K2 design environment continues to work in Chrome. For more information on the browser versions supported, please see the Support Matrix. Once Chrome has removed NPAPI support completely, the only workaround will be to use another supported browser (including Firefox, Safari or Internet Explorer 9 or greater). This workaround will no longer work in Chrome version 45 or when Google removes the option from Chrome, whichever comes first.
While Google Chrome continues to allow NPAPI to be re-enabled, you can enable the plugin by browsing to chrome://flags/#enable-npapi in Google Chrome. For additional timeline information, also see the Chromium Projects developer guide at. At this time Chrome will no longer be able to load those plugins. These components, found in every supported version of K2, only impact designers with the exception of the View Flow report.Īs documented in Google's Chromium Blog ( ), Google began phasing out support for NPAPI in January 2015 and they plan to completely end support for NPAPI in September 2015. These three components use Silverlight and therefore will no longer work in Google Chrome once NPAPI support is removed.
#Silverlight not working in chrome software
This breaks software packages like Microsoft’s Silverlight, which in turns breaks applications like Fidelity’s web based version of Active Trader Pro.
K2 blackpearl Cumulative Updates and Fixpacks In early September, 2015 Google stopped supporting NPAPI technology on Chrome.