Nice for them! We launched a web application for construction companies in Switzerland a few months ago. And quickly learned the hard way that we have to improve the IE compatibility. The last 90 days IE11 was used for 36% of all traffic. Too bad the new Edge isn't called IE12 and automatically deployed as a replacement through Windows Update :-)
ProtonMail is dropping support for Internet Explorer 11
41–50 of 63 posts
Re: ProtonMail is dropping support for Internet Explorer 11
#42Earlier quoted context omitted.
> Firefox's share is about the same as IE 11 (2.0 -> 2.5%). No? Most browser share analysis put FF at #2 (9-10%), for desktop/laptops and at #3 (5-6%) for mobile.
In minds of developers/managers/testers. I find too often sites that do not work correctly in Firefox.
Re: ProtonMail is dropping support for Internet Explorer 11
#43Earlier quoted context omitted.
The typical scenario is forced use by enterprises where the employees have no choice. But now that Windows 7 is on its last legs, this may be less of an issue.
You can have IE 11 on Windows 10. It's what I have, since the software we're working on use ActivX (to communicate with card reader software on the client machine); we should finally move to Chrome this year.
Re: ProtonMail is dropping support for Internet Explorer 11
#44I'd be pretty shocked if any ProtonMail users used IE.
It's the first bullet point in their reasons for dropping the support. About 1% of their users are on IE.
Re: ProtonMail is dropping support for Internet Explorer 11
#45Re: ProtonMail is dropping support for Internet Explorer 11
#46I understand them wanting to discontinue browsers that have very low usage and have discontinued support from Microsoft, but I can't help but feel a little sad about the narrowing browser engine ecosystem.
Exactly how many browser engines do we need? There's currently Blink(Chrome|Edge|Brave), Gecko(Firefox), and WebKit(Safari and various OSS browsers). With web technology standards, it doesn't really make sense that there would be that much competition, so having 3 competing engines seems sufficient to me.
Re: ProtonMail is dropping support for Internet Explorer 11
#47Nice for them! We launched a web application for construction companies in Switzerland a few months ago. And quickly learned the hard way that we have to improve the IE compatibility. The last 90 days IE11 was used for 36% of all traffic. Too bad the new Edge isn't called IE12 and automatically deployed as a replacement through Windows Update :-)
Sadly, Edge is completely different from IE, and still cannot replace it in most cases. There are still too many public websites (e.g. online banking and other sites using digital signatures), and even more enterprise intranet sites, that require legacy ActiveX, Java applets, or Silverlight. I'm fairly sure Microsoft is not fan of IE either, but they will still be stuck with it for many years. The most they can proba…
Re: ProtonMail is dropping support for Internet Explorer 11
#48Maybe I'll be able to reach other ProtonMail users here - does anyone else have persistent issues logging in to the web client? I use Firefox, LastPass, and Authy for 2FA. I have to try 6-7 times to log in every time, it drives me nuts. If it weren't for the mobile app I would have dumped this service long ago (for which I pay $50/year). This is the only site where I have issues logging in.
I've been using ProtonMail for about a year and I've never had an issue logging in. The web client is the primary interface I use.
Re: ProtonMail is dropping support for Internet Explorer 11
#49Earlier quoted context omitted.
Wouldn't be surprising to find that security conscious people are more apt to alter their user agent string or have a plugin that rotates it often to counter fingerprinting. There are probably fewer genuine IE11 users than what is being detected.
>or have a plugin that rotates it often to counter fingerprinting That's not going to fool any competent fingerprinting scripts. Blink/webkit/gecko have different javascript implementations so it's easy to cross-check whether your user agent header matches your "real" user agent. The only thing you're really going to fool are server side logs for user agent. If anything, using user agent spoofer is an entropy source…
Re: ProtonMail is dropping support for Internet Explorer 11
#50Earlier quoted context omitted.
Exactly how many browser engines do we need? There's currently Blink(Chrome|Edge|Brave), Gecko(Firefox), and WebKit(Safari and various OSS browsers). With web technology standards, it doesn't really make sense that there would be that much competition, so having 3 competing engines seems sufficient to me.
We need enough as to be reasonable competing point of views when it comes to setting standards. Things like web components, service workers, built-in javascript modules and more were pretty meh features pushed really hard by a specific browser vendor that tried to ignore feedback/pushback. The only way the standards won't get to be more of a mess is if we have multiple implementations and multiple, distinct organizat…
Browsers are basically an operating system now. For comparison, nobody cares that the Linux kernel isn't a standard. Nobody wants a "competing" Linux kernel implementation. The implementation itself is the standard and reference and that's totally fine.
The problem with looming IE dominance in the old days was that it was closed-source and proprietary, but that's not the case with modern day engines. In the FOSS world, competition isn't really a big driver. It just causes redundant work.
> A world where Blink has 80%+ marketshare (which is pretty much what we have or where we're headed) is one where a single group can dictate the standard for everyone else.
That's just not true. Any piece of software can be transformed into another piece of software. If really wants some feature I don't want, I can patch it out. If I publish some feature that thinks is good, they can just merge it.
Of course it would be good if was more like the LLVM-Foundation and not "literally Google", but the point is that having just one engine isn't the same as one party controlling the implementation. Microsoft obviously understands this, or they wouldn't choose Chromium as the new basis for Edge.