Vue 3 drops IE11 support plan

I work on a B2B app with a lot of local govt users. We dropped support officially for IE11 last summer and I was surprised by the little to no pushback.<p>Our stance was if you needed to use IE11 for a legacy application, that&#x27;s fine -- but our application required something besides IE and you&#x27;re not limited to only one browser on your computer.<p>Any stances by IT that they haven&#x27;t had a chance to authorize another browser or prove that another browser was secure compared to IE11 is an absolute joke at this point. Any IT department that is telling users to use IE11 for security reasons is questionable imho.

I&#x27;ve been keeping a log of the slow death of IE here: <a href="https:&#x2F;&#x2F;twitter.com&#x2F;swyx&#x2F;status&#x2F;1260627626739130369?s=20" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;swyx&#x2F;status&#x2F;1260627626739130369?s=20</a><p>in the past year, major sites in all categories from linkedin to twitter to skillshare to microsoft to adobe have all dropped IE, with Wordpress, Drupal and Vuejs making plans.<p>The big catalyst I think will be the US government dropping IE support - it only supports browsers above 2% usage (<a href="https:&#x2F;&#x2F;github.com&#x2F;uswds&#x2F;uswds&#x2F;issues&#x2F;3877" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;uswds&#x2F;uswds&#x2F;issues&#x2F;3877</a>), and we are currently hovering at 2% dropping 0.1% a month <a href="https:&#x2F;&#x2F;analytics.usa.gov&#x2F;" rel="nofollow">https:&#x2F;&#x2F;analytics.usa.gov&#x2F;</a>

I&#x27;m not even joking when I say this, for some companies, it would literally be cheaper to buy your IE users a new computer. Obviously, for enterprise customers, who are likely to be the majority of IE 11 users, you can&#x27;t necessarily do that (though think about if you can).

I still use IE as my default browser (and Firefox as a fallback), for the following reasons:<p>– The font rendering works better for my eyesight.<p>– Killer feature: Ctrl+N&#x2F;K clones the browser window&#x2F;tab <i>including</i> the history. I.e. you can effectively fork the history. EDIT: And, equally important, opening a link in a new tab&#x2F;window also preserves (clones) the history.<p>– Certain keyboard operations have better usability than on other browsers.<p>– The title bar + address&#x2F;tab bar height height is smallest among all browsers (after some configuration).<p>I’m slowly getting used to the inevitability of migrating to Firefox. The font rendering and especially the clone-by-keyboard feature are the hardest part though. (And the fact that Firefox doesn’t allow yellow as a search highlight color.)

I&#x27;ve heard that the people who use IE11 are the ones who don&#x27;t have a choice, because maybe they are using a computer at a library, or some kind of accessibility-related device. Does anyone on HN know of solid data to back this claim? This screenreader[1] survey for example says 11% of their users use IE11, though that is from 2019.<p>[1] <a href="https:&#x2F;&#x2F;webaim.org&#x2F;projects&#x2F;screenreadersurvey8&#x2F;#browsers" rel="nofollow">https:&#x2F;&#x2F;webaim.org&#x2F;projects&#x2F;screenreadersurvey8&#x2F;#browsers</a>

Coincidentally, Angular is going to deprecate IE11 support with Angular 12, and remove it with Angular 13<p><a href="https:&#x2F;&#x2F;blog.angular.io&#x2F;angular-v12-is-now-available-32ed51fbfd49" rel="nofollow">https:&#x2F;&#x2F;blog.angular.io&#x2F;angular-v12-is-now-available-32ed51f...</a>

Microsoft Teams already chopped it, with Office 365 not far behind.<p><a href="https:&#x2F;&#x2F;techcommunity.microsoft.com&#x2F;t5&#x2F;microsoft-365-blog&#x2F;microsoft-365-apps-say-farewell-to-internet-explorer-11-and&#x2F;ba-p&#x2F;1591666#:~:text=Beginning%20November%2030%2C%202020%2C%20the,like%20the%20new%20Microsoft%20Edge" rel="nofollow">https:&#x2F;&#x2F;techcommunity.microsoft.com&#x2F;t5&#x2F;microsoft-365-blog&#x2F;mi...</a>.

I definitely think they made the right call here. Even Microsoft is dropping support in Office 365.<p>Commendable, too, that they are working to backport some v3 features to the v2 codebase.

We have found that refusing to support IE11 in healthcare environments has lost us 0 customers and given them a reason to move away from it. At this stage any company using it and the likes windows xp or windows 7 are just creating unnecessary security risks.

I hope this is the last time I read Vue and IE11 in the same sentence. Actually, I hope this is the last time I read IE11 in any sentence.

TBH the only reason some clients are all the way on IE11 is because IE10 doesn&#x27;t support TLS1.2, so they HAD to move to pass a security audit.

I have no love for IE, but does anyone remember when we designed web pages to work on any browser?

- Not even supported by Microsoft apps like Teams<p>- Easily less than 1% market share<p>- IE11 is side by side packaged with some version of Edge in almost every case<p>This seems reasonable.

You can&#x27;t have evolution without dropping ties to the past from time to time. That&#x27;s about time to drop IE11 to take full advantage of modern Web features.

Heh, so we really ought to move from MSHTML... We&#x27;re embedding a web browser control in our app for flexibility in adapting the GIS documentation system to varying needs depending on customer. Some customers document more details on electricity meters than others, some tie them to other billing systems on the backend than others. Etc...<p>But it&#x27;s actually working out great and we can as a bonus update these parts of the desktop app without even shutting it down. Our app has a web API that the scripts interact with.<p>The obvious downside is that it&#x27;s using IE 11. WebView2 exists though which uses Microsoft&#x27;s Chromium fork, but the control is only now reaching production quality. Like mere months ago. <a href="https:&#x2F;&#x2F;docs.microsoft.com&#x2F;en-us&#x2F;microsoft-edge&#x2F;webview2&#x2F;" rel="nofollow">https:&#x2F;&#x2F;docs.microsoft.com&#x2F;en-us&#x2F;microsoft-edge&#x2F;webview2&#x2F;</a><p>But it&#x27;ll probably be what we eventually do especially as it supports Windows 7 which is quite something for emerging technology from Microsoft. We need this because surprisingly many customers still have Windows Server 2012 installs here and there. Sounds insane to run 10 year old servers for security reasons but the amazing thing is that Microsoft will support these to late 2023.<p>For now we&#x27;re in our most advanced scripts using Bootstrap Vue + VueJS 2 + a few polyfills and it&#x27;s amazed me how seamless it actually is in developing on Chromium 90 and everything just keeps working and looking almost identical on IE 11. Interaction, model bindings, templating, everything. I totally did NOT expect this. I expected... &quot;Support&quot;. I mean... This is some achievement. There&#x27;s been the occasional, minor stumbling block every three months or so but still...

Even though I&#x27;ve more or less zero IE11 users on Upstract, I still make sure that everything renders and basically works on it — I think this defensive, vanilla, bare-metal, no-gimmicks mindset creates better and simpler products — in spirit of what old-school Web tech was about.<p>(Unless you&#x27;re building something like Figma of course).

IE11 is the last IE; not sure if people realize that this actually means &quot;We&#x27;re dropping support for Internet Explorer&quot; and not just a single version.

Bootstrap 5 released last week also dropped IE11 and &quot;legacy&quot; Edge.

This is obviously great overall, developing for IE is a pain. One weird anecdote though, I have an old laptop that has very little memory, running Windows 10. And I swear, IE11 works better than Chrome and Edge for websites that support it. Chromium seriously seems to crash my computer because of some memory issue. Any idea why this happens (regarding IE performing better)?<p>I only know this because I maintain a CSS framework that supports IE11, so I have to use IE quite a bit.

I&#x27;m currently building a website that uses Vue 3 in parts, as well as other features that don&#x27;t work (well) in IE11 such as CSS Grid.<p>Would you recommend only displaying an error screen for any users who try to view the site using Internet Explorer or another old browser? Or should I let those browsers try to display what they can, and maybe also a warning message?

When looking at IE users, the percentage of users using only IE would be smaller.<p>Especially, since microsoft is now supporting MS edge on windows 10.<p>Moreover even if some old app is using vbscript or some arcane IE only stuff, then they are unlikely to modify the app,let alone adopt Vue.

I am counting down the days until our customers stop using IE11, most of them offer the option of IE11 or Edge.<p>We have so little traffic from it now, and the browser renders far slower than Edge &#x2F; Chrome. Habits are hard to kick in enterprise.

Any chance we can keep supporting java applets ? Still need them to fill up my hours.

Talking about vue, I&#x27;m really waiting for Vuetify to support Vue3. Especially with typescript I feel like the current ways to describe fragments are a bit half-assed.

IE11 is supposedly at 1% market share. However, Vue market share is 0.77% of all websites (which is actually huge) Therefore, even for those 1% users of IE11, that&#x27;s still like 1 of the hundred pages they&#x27;ll visit in a day. And because so many other frameworks already killed IE11, it&#x27;s not like those 1% users are going to complain too much more than they would already be, oh shit now 2 of the 100 pages I visit per day are blank!

IE11 is basically the last browser that has a sane non-infantilising UI and per-site configuration by default. It works great for the non-JS sites, better than Dillo and Netsurf at least.<p>I use it as a way to say &quot;Fuck the Google monopoly.&quot; Firefox is slowly going down that path too, because they haven&#x27;t a chance at opposing the giant.

I wondered if this might happen when I first read that they were planning to release a Vue 2.7 backporting some 3.0 features to the 2.x branch.<p>Never seemed much point doing that <i>and</i> an IE port of 3.0, especially considering that 2.x works great on IE (even back to IE9 with transforms and polyfills!) if you absolutely have to support it.

Webmasters should redirect their IE users to <a href="https:&#x2F;&#x2F;browser-update.org&#x2F;update.html?force_outdated=true" rel="nofollow">https:&#x2F;&#x2F;browser-update.org&#x2F;update.html?force_outdated=true</a>

Who still uses IE11 anyway?

At our company we’ve now switched it around. Instead of expending effort making new applications work in IE11, we expend a much lesser effort making legacy applications work in Chrome.

Is anyone working on enterprise-level apps that see a significant number of conversions from IE11 right now?<p>I&#x27;m surprised to learn a framework the size of Vue was still supporting it until now.

Legitimate question: what companies (I&#x27;m assuming it&#x27;s government) done have Chrome or Firefox installed? What is this IE compatibility caused by?

What&#x27;s the biggest thing that IE 11 is missing that gives devs the most grief?

here we go again

what is IE11?

I use IE6 as a sort of litmus test for websites. If a site works in IE6, it&#x27;s more likely to work on every browser imaginable. Those people creating sites designed to work in the latest browser version only scare me to death.