ProtonMail is dropping support for Internet Explorer 11
31–40 of 63 posts
Re: ProtonMail is dropping support for Internet Explorer 11
#32Earlier quoted context omitted.
Last major update for IE11 was like 6 years ago? Supporting anything related to this browser is painful and is blocking multiple new web features (or even not so new). I would love to use CSS Grid without thinking whether it will work however it happens that IE11 has only partial (and buggy) support for it. I believe that supporting IE11 blocks innovation.
What sort of features does a mail client need though? Up until recently i was using SquirrelMail and only stopped because my webhost removed it (likely because there hasn't been an official release for a few years now... which is weird since there is progress in the code repository, just not official releases). In case you haven't used it, SqurrelMail barely uses anything beyond a couple of frames (normal ones, not i…
Re: ProtonMail is dropping support for Internet Explorer 11
#33Earlier quoted context omitted.
What sort of features does a mail client need though? Up until recently i was using SquirrelMail and only stopped because my webhost removed it (likely because there hasn't been an official release for a few years now... which is weird since there is progress in the code repository, just not official releases). In case you haven't used it, SqurrelMail barely uses anything beyond a couple of frames (normal ones, not i…
I'm sort-of supporting IE11 at my current company and it's not about the features, IE11 is full of rendering bugs & quicks which make you work more. Lots of CSS bugs, lots of JS bugs, it's just an outdated browser which has a real cost to support. Then you need to be careful to include enough polyfills because even what you assume would be there probably isn't, there's no Promises, no Array.prototype.includes, no arr…
Re: ProtonMail is dropping support for Internet Explorer 11
#34Earlier quoted context omitted.
I'm sort-of supporting IE11 at my current company and it's not about the features, IE11 is full of rendering bugs & quicks which make you work more. Lots of CSS bugs, lots of JS bugs, it's just an outdated browser which has a real cost to support. Then you need to be careful to include enough polyfills because even what you assume would be there probably isn't, there's no Promises, no Array.prototype.includes, no arr…
So it isn't a case of something being impossible but more of a case that it needs workarounds to make things work with it?
Re: ProtonMail is dropping support for Internet Explorer 11
#35Earlier 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.
I'm sure some won't like this comment, but there are only two that matter: Chrome and Safari. 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.
Re: ProtonMail is dropping support for Internet Explorer 11
#36We 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 :-)
Re: ProtonMail is dropping support for Internet Explorer 11
#37Earlier 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
#38I'd be pretty shocked if any ProtonMail users used IE.
Yes that seems a pretty odd combination, you want more secure email but using IE11 at the same time?
Re: ProtonMail is dropping support for Internet Explorer 11
#39Nice 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 :-)
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 probably do, is to not have it installed by default in future versions of Windows 10, but I have a feeling that it will stick around for longer than IE6.
Re: ProtonMail is dropping support for Internet Explorer 11
#40Earlier quoted context omitted.
I'm sure some won't like this comment, but there are only two that matter: Chrome and Safari. Firefox's share is about the same as IE 11 (2.0 -> 2.5%).
> 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.