Page 1 of 1

NPAPI Depreciation in Chrome

Posted: 15 Apr 2015
by dstgroup
As of today Google has now turned of NPAPI by default in Chrome 42. As a result Silverlight no longer functions. There is a switch that allows turning it back on ,but only until Sept when it will be removed completely from Chrome.

What are the plans for the form designer as we see browsers moving away from plug ins etc?

Re: NPAPI Depreciation in Chrome

Posted: 16 Apr 2015
by Dmitry Kozlov
Hi,

Thanks for the question. The Silverlight is used by the designer only, it doesn't affect final forms. So, you will be able to customize forms in any other browser, say, IE.

Re: NPAPI Depreciation in Chrome

Posted: 16 Apr 2015
by dstgroup
I realize it is only the designer. However Chrome is not the only browser with the issue. MS plans to make Spartin the default Browser in Win 10 and it too doesn't support plug ins. I take that to mean MS is also depreciating them.

So I was wondering if there were plans for that issue.

Re: NPAPI Depreciation in Chrome

Posted: 16 Apr 2015
by Dmitry Kozlov
Well, most likely, the RTM version of Spartan will support Silverlight andJava as well. Anyway, Spartan and IE11 will coexist in Windows 10, so you will be able to use IE11 to design forms. Currently, Silverlight is the fastest technology for such applications as Forms Designer. We compared our solution with other designers based on HTML/JS and found out that our app is much more stable, fast and easy-to-use, thanks to Silverlight and our developers, of course :)