by alexobenauer on 6/15/22, 2:33 PM with 206 comments
by wolframhempel on 6/15/22, 2:41 PM
- creating sprite sheets of transparent png corners and sides that one could arrange in a table around an element to create drop-shadows and rounded corners
- putting single pixel, transparent gifs at the end of floated containers because clearfix used a "before" CSS selector that earlier IEs didn't know about.
- writing CSS rules like -ms-filter: "progid:DXImageTransform.Microsoft.Alpha(Opacity=75)"; to make something semi-transparent...
And so much more. Back then, we were certain we'd open a bottle of champagne once IE is not a requirement anymore.
Today, fortunately, I have a different Job and Microsoft makes different browsers. But looking back, I wouldn't have believed this day to arrive.
by jrochkind1 on 6/15/22, 4:05 PM
> Windows releases where Internet Explorer will still be available after June 15, 2022, include Windows 7 ESU, Windows 8.1, and all versions of Windows 10 LTSC client, IoT, and Server.
> "The Internet Explorer (IE) 11 desktop application will end support for Windows 10 semi-annual channel starting June 15, 2022," Microsoft says on the IE11 lifecycle page.
> As Microsoft further explains, "for supported operating systems, Internet Explorer 11 will continue receiving security updates and technical support for the lifecycle of the Windows version on which it is installed."
https://www.bleepingcomputer.com/news/microsoft/internet-exp...
I gotta say... MS is serious about long-term support commitments and backwards compat!
by pavlov on 6/15/22, 4:25 PM
25 years after the release of IE4, I'm just glad both of those browser codebases are now dead.
IE was really done in by Microsoft's "Longhorn" OS project. After Windows XP, Microsoft was planning a very ambitious update that would completely reset core APIs. File systems would be largely replaced by an OS-level database, and the Win32 GUI API would be replaced by an XML-based UI framework codenamed Avalon.
A new Avalon browser would ship with the OS, and thus IE + HTML would become legacy technologies as Microsoft confidently assumed most developers would flock to building their web apps in Avalon instead.
To Microsoft strategists, it seemed that they had succeeded in containing the web: Netscape was dead, Mozilla had almost no users, Apple was shipping their IE in Mac OS X, Google wasn't on Microsoft's radar, and the HTML standard process was stalled. So while a lot of content was being delivered as HTML4, there didn't seem to be any reason left for Microsoft to invest in IE — they'd already nailed the browser, owned the market, and would push Avalon as the next step.
Fortunately, Longhorn failed. Some parts of the project eventually shipped years late as Windows Vista. Avalon became WPF + XAML and still exists in Windows, but the dream of a XAML browser replacing IE was dead.
by philliphaydon on 6/15/22, 2:54 PM
by tiborsaas on 6/15/22, 3:15 PM
<meta http-equiv="X-UA-Compatible" content="IE=edge,chrome=1">
https://docs.microsoft.com/en-us/openspecs/ie_standards/ms-i...This will make IE very insisting to upgrade to Edge if possible.
by psim1 on 6/15/22, 3:29 PM
by err4nt on 6/15/22, 2:50 PM
by intrasight on 6/15/22, 3:56 PM
But I really dug into SPA/AJAX web apps in 2000 - building enterprise stuff. They were all "IE6 apps". IE6 was basically my X-windows. No other browsers were supported, and there as no pushback from customers back then. Only one of those apps made the transition to IE11.
Last year I explained to my current client that our big enterprise reporting app had to move off IE11. And I was really surprised how much pushback on got on that.
by open-paren on 6/15/22, 2:54 PM
by wonderbore on 6/15/22, 3:51 PM
This news is meaningless. This confirms it:
> For supported operating systems, Internet Explorer 11 will continue receiving security updates and technical support for the lifecycle of the Windows version on which it is installed.
From https://docs.microsoft.com/en-us/lifecycle/faq/internet-expl...
by timeimp on 6/15/22, 2:39 PM
Any apps / mainframes / industrials systems that needs IE to run?
by layer8 on 6/15/22, 3:03 PM
- crisper and higher-contrast font rendering on low-DPI monitors
- Ctrl+N/Ctrl+K clone the current tab into a new window/tab including its history, letting you “fork” the tab and effectively navigate a history tree. Edit: And, maybe more importantly, opening a link in new window/tab also clones the history.
- generally good keyboard usage, e.g. for the history tab (you can for example always blindly hit Ctrl+H, Home, Enter to go to the last visited page, something which is more fiddly in other browsers)
- larger viewport height than possible on Chrome/Firefox/Edge (after hiding the toolbar and status bar, configuring tabs to be on the address bar, etc.)
- allows yellow search highlighting (which Firefox doesn’t on light backgrounds)
by user_7832 on 6/15/22, 4:11 PM
Does anyone (especially from MS) know why later versions of IE and pre-chromium Edge were so good and snappy with scrolling? The level of accuracy and speed was incredible (on touchpads at least) - it was probably the last time I had an interaction on a computer that made me go "wow".
by lemoncookiechip on 6/15/22, 2:55 PM
The King is dead, long live the King.
by night-rider on 6/15/22, 2:38 PM
by maxpert on 6/15/22, 3:35 PM
var request = new ActiveXObject("Microsoft.XMLHTTP");
by logifail on 6/15/22, 2:51 PM
[0] https://docs.microsoft.com/en-us/windows/whats-new/ltsc/ [1] https://docs.microsoft.com/en-us/lifecycle/faq/windows#what-...
by konfusinomicon on 6/15/22, 2:45 PM
by xutopia on 6/15/22, 3:06 PM
by mwcampbell on 6/15/22, 2:57 PM
by newbieuser on 6/15/22, 9:13 PM
by ChrisArchitect on 6/15/22, 7:36 PM
by aquova on 6/15/22, 4:04 PM
by philliphaydon on 6/15/22, 2:36 PM
by charles_f on 6/15/22, 3:05 PM
by kazinator on 6/15/22, 3:53 PM
I made to the web UI of a firmware device, and needed to check whether it will work with old browsers as far back as IE9.
Because IE11 has an emulation mode, I didn't have to install IE9.
Thank you, IE11!
:)
by ricardobayes on 6/15/22, 2:48 PM
by caycep on 6/15/22, 6:47 PM
(note, they say they are compatible with Edge etc. But sadly they are really not)
by 2000UltraDeluxe on 6/16/22, 7:40 AM
by sbf501 on 6/15/22, 3:04 PM
by major505 on 6/15/22, 8:25 PM
by Agamus on 6/15/22, 5:51 PM
Thank you, IE - and good riddance!
by 101008 on 6/15/22, 6:11 PM
by hidden-spyder on 6/15/22, 5:43 PM
by kasajian on 6/15/22, 5:26 PM
by throwaway71271 on 6/15/22, 2:50 PM
only webkit is left
the king is dead, long live the king.
by pmarreck on 6/15/22, 4:47 PM
by Spooky23 on 6/15/22, 6:00 PM
by bombcar on 6/15/22, 2:40 PM
by upupandup on 6/15/22, 2:44 PM
by Mattmrmatt on 6/15/22, 4:21 PM
by brainyz on 6/15/22, 2:37 PM
by geniium on 6/15/22, 4:25 PM
by DrBazza on 6/15/22, 2:40 PM
At least it's not hard wired into the OS and we're not going through another era of mega-corp hard wiring browsers into their OSes any more.
Oh wait.
by neatze on 6/15/22, 2:47 PM