Earlier quoted context omitted.
Imagine being the engineer who has to keep maintaining the IE codebase for the next 8 years. [shudders]
This must be what hell is like.
Internet Explorer 11 (IE11) to be retired on June 15, 2022
131–140 of 304 posts
Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022
#132I smell a lot of nostalgia in this thread, and rightfully so! IE has been a terrible browser, but it was our terrible browser. But fear not! Outlook still uses the HTML parsing engine from MS Word (!) to display your HTML emails, and it's not going anywhere.
My biggest ever frustration.
Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022
#133Earlier quoted context omitted.
But Gmail is already a web app, and only supports a tiny subset of modern HTML and CSS. The limitation is of course arbitrary, it could in theory support any modern standards. But HTML mail is so quirky and full of hacks, that they probably have to do it that way to preserve compatibility. Apple's Mail app is one of the few modern mail clients that can render modern HTML/CSS
That's true, and I wish that emails could just work like everything else on the web. But simply removing Outlook and all its baggage from the equation would be a big, big improvement on the status quo.
Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022
#134Earlier quoted context omitted.
Imagine being the engineer who has to keep maintaining the IE codebase for the next 8 years. [shudders]
I’m pretty sure almost no one is. There are tons of IE11 layout bugs (not missing features, straight-up bugs) that have not gotten fixed in 8 years. I get the vibe that MS may have totally cut off development and all but the most critical security maintenance in order to speed the plow of Edge adoption.
Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022
#135Earlier quoted context omitted.
In an AD environment, you can push out a centralized list that is easy to update. We've found that IE Mode unfortunately works very well. I wish it didn't work so well because it allows us to keep these IE sites around indefinitely.
While it keeps existing IE11 compatible sites around indefinitely, it stops everyone else from having to support IE11 because that's the default and only browser IT allows on the machine.
Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022
#136Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022
#137I work on a SaaS app in the healthcare space where IE11 is the preferred browser, and was getting worried watching all of our favorite tools begin to completely drop IE11 support (Tailwinds, Bootstrap) - effectively punishing us for the sins our customers IT orgs. This brings me hope. But only a little. I’m sure they’ll find a way to keep running it.
Isn't IE11 support a potential HIPPA violation?
Also...no? Why would it be?
Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022
#138I work on a SaaS app in the healthcare space where IE11 is the preferred browser, and was getting worried watching all of our favorite tools begin to completely drop IE11 support (Tailwinds, Bootstrap) - effectively punishing us for the sins our customers IT orgs. This brings me hope. But only a little. I’m sure they’ll find a way to keep running it.
Isn't IE11 support a potential HIPPA violation?
To the extent (if any, though I'd be surprised if there were none) IE11 doesn’t support standards required effectively, if indirectly, via the HITECH guidance on secured PHI, IE11 use could have some some adverse consequences under HIPAA (and, as a SaaS operator with a BAA that would include the vendor, not just the customer), but not in and of itself noncompliance for use or support. Mostly just making it more likely that situations would become reportable breaches.
Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022
#139Now ship WebView2 with the OS in a reliable way that people can use.
Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022
#140Earlier quoted context omitted.
That's true, and I wish that emails could just work like everything else on the web. But simply removing Outlook and all its baggage from the equation would be a big, big improvement on the status quo.
There are good reasons to reject a lot of it. You don't want JS running in an email for example. Or even some of the fancier CSS abilities.