Chrome has already dropped its NPAPI (silverlight) support
Firefox has announced it will stop NPAPI support as of the end of 2016 (https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/)
Edge did not support NPAPI from the start
InternetExplorer is supporting it untill 2021 (https://support.microsoft.com/en-us/lifecycle?c2=12905)
Are there any official announcements on the Safari front?
The only thing "official" at this time is that the Get Silverlight page now cites 31 Dec 2016 as the end of support for Silverlight in Safari. However, as I noted in this question it remains unclear if that date was set by Microsoft, or by Apple planning the end of NPAPI support.
Update June 2016:
On the WebKit blog the Safari team has announced that
When Safari 10 ships this fall, by default, Safari will behave as
though common legacy plug-ins on users’ Macs are not installed.
The goal is to steer site to use HTML5. However they do say:
If you can’t replace a plug-in-based system in the short term, you may
want to teach your users how to enable that plug-in for your website
in Safari.
So the end of any Silverlight support in Safari remains officially unannounced.
Update Nov. 2016:
Webkit Release Notes for Safari Technology Preview 17 state:
Removed NPAPI Plug-in support from .safariextz Safari Extensions
but a date for mainstream release is not given. End of 2016 seems plausible.
Update Jan. 2017
From my testing Safari has not yet (1/11) been updated to include the loss of NPAPI support which was part of Safari Technology Preview 17. So far as I can see it is anyone's guess what their schedule is.
Firefox ver 52 mainstream release is scheduled for Mar. 7 2017 and according to here and the bug tracker. That is the last one to support NPAPI. This sure looks like the end of the road for Silverlight on Mac, unless you move to the ESR release v 52.x of Firefox, which will keep it available for a while. My reading of the ESR release schedule is that it may go to Q1 2018, but interpret that for yourself.
Update Mar. 27, 2017
Safari 10.1 was released and Safari still supports Silverlight, but it must be enabled with each use.
Related
I'm planning to use IndexedDB Wrapper Dexie.js for my react.js application.
Does Dexie.js support all kinds of web browsers?
If there is any limitation, kindly let me know
Thanks in advance.
Dexie.js supports all major modern browsers including but not limited to:
Chrome - all versions younger than 7 years.
Firefox - all versions younger than 7 years.
Safari - all versions younger than 3 years.
Opera - all versions younger than 7 years.
Edge - all versions younger than 3 years.
Internet Explorer 11 - partial support
Edge legacy - partial support
Select2 does indicate its support for desktop browser version to be: IE8+, Chrome 8+, Firefox 10+, Safari 3+, Opera 10.6+
However, I cannot find anything regarding Mobile & Tablet support.
Is there any official statement I have missed?
Simply quoting from the same question I asked on the Github project
Select2 3.5.x should work well in all of the latest mobile devices.
It's used in many large websites and we've appeared to have ironed out
many of the old issues.
Select2 4.0.0 has not yet been released, but Beta 3 has been tested to
work with Android devices without any real issues. We don't have any
iOS devices to test on, but more than likely they work well on iOS as
well.
Quoting from same question, for version 4.0.3 ( current stable release )
Yes, this version is more stable. Tested on Android 6.0.1 and iPhone 6.
I have a Silverlight 3 application that contains 1 code line (it's a part of real project):
var doc = HtmlPage.Document;
In Safari 5.1 (Windows 7 SP1, Silverlight plugin 5.0.61118.0) I get the Exception in this line:
Unable to cast object of type System.Windows.Browser.HtmlElement to type System.Windows.Browser.HtmlDocument
So, I don't have any access to browser DOM model.
In other browsers everything is ok.
Can somebody help me with this if it's possible ?
I have the same problem, it seems to only occur on Safari for Windows with the Silverlight plugin 5.0.61118.0. The problem seems to have been introduce with Silverlight 5.0.
Also, you cannot access: HtmlPage.Window
According to Microsoft officially Safari for Windows is not a support platform, see:
http://www.microsoft.com/getsilverlight/Get-Started/Install/Default.aspx (click System Requirements)
In my testing I found that the issue does NOT occur in Silverlight 4 but DOES occur in Silverlight 5.
This is slightly confused because if you try to install Silverlight 4 on Safari for Windows from this link:
http://go.microsoft.com/fwlink/?LinkID=149156&v=4.0
Then you end up with a Silverlight 5 installation.
I found that you use IE to visit this link then Save the download EXE, then install the EXE on Safari for Windows you will get a Silverlight 4 install and from my testing this works. Thus, I am advising my customers who face this issue to install Silverlight 4 as described.
Try this and see if this works (my application uses the navigation framework):
As the error has something to do with the NavigationJournal and in SL we have some control over it I just changed the Journal ownership to:
sdk:Frame JournalOwnership="OwnsJournal"
On the MainPage.xml where the navigation takes place in my app. In this way we lose the browsers back button/navigation but we can implement our own inside the SL app.
I am starting to write an xbap (wpf web app).
I create a new project and run it and Firefox fails (it just keeps trying to open it with "Windows Presentation Foundation Host).
I know that Firefox and Microsoft don't really see eye to eye, but surely there is a way to do this now days?
Saw this post that shows a hack of copying out a DLL from a Windows XP machine. But my users will not do that (I don't even want to do that!)
Does this mean I have to abandon Firefox as my default browser until I am done developing my xbap?
NOTE: I am using Windows 7 and Visual Studio 2010 Ultimate and Firefox 3.6.12
I don't know what exactly your problem is, but here is a Scott Hanselman blog post detailing a WPF application deployed as an XBAP (not XBAB) using VS 2008 with .NET 3.5. It doesn't say anything about WPF 4 (and the .NET 4 runtime, the post is from 2008) or what version of Firefox he was playing with but I hope this demonstrates it is possible and gives you a starting point for more detailed investigations.
Edit - Well, I should have dug a little deeper. It appears that Windows 7 won't support XBAPs in FireFox. There is a Firefox Add-on to Support XBAPs and Loose XAML that is installed with the .NET 3.5 runtime but it is not included in Windows 7 and this link suggests it can't be installed on Windows 7.
You could run IE Tab Plus (Firefox plug-in) and get it to default to IE when you open something from the localhost.
Is Silverlight for Mobile now available as of today, April 21, 2010?
Is it supported in Windows Mobile 6 phones? I read that it will only be supported in Windows 7 Phones
http://arstechnica.com/microsoft/news/2010/02/can-silverlight-save-windows-mobile-from-plummeting-sales.ars
The Developer Tools can be downloaded here, but there aren't any Windows Phone 7 devices released yet.
Is Silverlight for Mobile now available?
It is still in Community Technical Preview for Windows Phone 7 (as of 21 April 2010) and it is not compatible with Visual Studio 2010 RTM Version. The emulator is supposed to be pretty good so we can develop against it.
Is it supported in Windows Mobile 6 phones?
It is not available for WM6 (yet). I am not sure with their plan.
from Wikipedia:
The first Community Technology Preview (CTP) for Windows Mobile 6 was
expected in the 2nd Quarter of 2008,
but it still not officially announced.
Microsoft has stopped focusing on
bringing Silverlight to Windows Mobile
6.x and is planning to include it in Windows Mobile 7.[55]
Last month I read this blog-article about an "open source clone" of silverlight coming to Iphone. I'm very curious about this
http://www.downloadsquad.com/2010/03/14/novell-to-bring-open-source-silverlight-clone-to-iphone/