Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Internet Explorer 11 (IE11) to be retired on June 15, 2022

blogs.windows.com

Post reply on HN
Print view View original

291–300 of 304 posts

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#291

Post by potemkinhr »

unilynx wrote: post #282
potemkinhr wrote: post #274

IE is used in some unexpected places, one of the weirder ones for example a ingame display frame for the ingame wiki of older Total War series games. They'll need to update the game and replace it in some way else ingame help will be unavailable when they remove it via an update.

Are they actually using IE or just the webview? As far as I understand, that one is staying around for a couple of more years

It's probably just WebView but from the UI and elements it was obvious that it's IE-based. What's also interesting is that for the manual's videos Flash was required which now obviously doesn't work as it was removed via cumulative updates on W10

https://steamcommunity.com/app/34330/discussions/0/864947668...

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#292

Post by drewzero1 »

derefr wrote: post #192
djxfade wrote: post #117

Earlier 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

Given that email is MIME (i.e. you can add multiple “bodies” to a message, with different content-types, and the email client will select the best one it can render), you’d think we could just come up with a new content-type for email meaning “HTML, but for real”, and add that to email in addition to the current “HTML, but sucky” semantics we get from text/html-typed bodies. For a while, people would be sending both…

> a new content-type for email meaning “HTML, but for real”

text/email Mozilla/5.0 (KHTML, like Gecko)

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#293

Post by dotancohen »

ido wrote: post #204
detritus wrote: post #112

Earlier quoted context omitted.

Oh, don't get me wrong - it was a Trojan Horse, and my first ever web browsing experience was on Navigator, so it was a hard-hearted appreciation at the time. But from my stand point then, It Just Worked.

Same for me - I started browsing the web on Mosaic and quickly switched to Netscape. I hung on during the Netscape 4.x days but at some point couldn't deny how much better IE was (I think maybe even IE 4 was already as good or better than Netscape). I switched to IE until the Mozilla suit released and later on switched to Firefox 0.something - it was amazing how fast it was compared to both IE6 and Mozilla.

Some time around 2001 or 2002 I bought Opera (with tabs!) and that just made the internet usable.

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#295

Post by derefr »

drewzero1 wrote: post #292
derefr wrote: post #192

Earlier quoted context omitted.

Given that email is MIME (i.e. you can add multiple “bodies” to a message, with different content-types, and the email client will select the best one it can render), you’d think we could just come up with a new content-type for email meaning “HTML, but for real”, and add that to email in addition to the current “HTML, but sucky” semantics we get from text/html-typed bodies. For a while, people would be sending both…

> a new content-type for email meaning “HTML, but for real” text/email Mozilla/5.0 (KHTML, like Gecko)

I get what you mean, but it's not like we'd have to keep adding these on. "text/html" on email clients currently means "some specific ossified version of HTML4"; but text/html-for-real would hopefully mean "the newest and most featureful version of HTML that your rendering engine can manage." So there'd just be the one version of it.

Eventually, if everybody switched to sending text/html-for-real first, maybe the email clients could follow along and make text/html also mean "the newest and most featureful version of HTML5"; and then we could all revert to just calling it text/html.

Rather than a distinct MIME type, I believe it could also make sense to borrow the HTTP header X-Content-Type-Options: nosniff (https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-...) into the MIME envelope of the text/html document, to signal that this envelope is "really" using HTML, no second-guessing. (This is how the header was used in IE8: to tell the renderer to explicitly not trigger IE historical-renderer compat mode.)

That might get into a situation where the message has two MIME bodies that are both text/html, though, and I'm not sure existing clients have been written to cope with that. A well-engineered solution would work with existing clients (by having them ignore the body of unknown-to-them media-type, and render the old fallback body of known media-type.)

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#296

Post by torstenvl »

chociej wrote: post #288
torstenvl wrote: post #59

Earlier quoted context omitted.

Not accusing you of this, but the primary reason people run outdated software is a really problematic insistence, mostly by front-end people, on using the new-and-shiny instead of the tried-and-true. Breaking changes galore - so people stick with the past as much as possible. Example: Office 365 OWA doesn't work well on modern browsers other than the latest version of Edge on Windows. But it does work fine on browser…

I dislike Outlook 365 because of a number of UX design decisions, but I can't say it works poorly on Firefox for me.

For me, and maybe this is just my organization, but the new O365 OWA interface is extremely slow. Latency is so bad that typing results in only 1 in every 4-5 keystrokes not failing to register.

If I pretend my user agent is from circa 2012-2013 (e.g., Internet Explorer 10), it will default to an older interface that has marginally fewer features and is much, much more performant.

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#298

Post by brailsafe »

easton wrote: post #80
skrebbel wrote: post #74

I 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.

When Outlook becomes a PWA (currently in test, I think it's probably two-three years from stable), it'll be rendering mail with all the functionality of Blink. Which depending on your point of view, means a sigh of relief or time to buy more RAM. https://www.windowscentral.com/project-monarch-outlook-web-u...

I'm pretty ok with emails just being barely more than text thank you

Re: Internet Explorer 11 (IE11) to be retired on June 15, 2022

#299

Post by gnu8 »

Notre1 wrote: post #142
detritus wrote: post #126

Earlier quoted context omitted.

Nope, still using two of their products today, and waiting for the moment (as, I think, promised soon?) wherein I could donate/pay directly to/for firefox. I don't broadly support Mozilla's aims (I also don't not - I'm an owner of a 1st-gen Firefox phone, for example), but we're just talking browsers here.

I think you proved his point. ;) He's talking about the Mozilla browser, the precursor to Firefox. (Well actually, Firefox was named Phoenix before it became Firefox.)

Right and my memory is telling me that I was using it since one of the milestone releases, well before 0.9.5 when they added tabbed browsing.
Post reply on HN