IE 11 is still supported by Microsoft because it is tied to Windows 10 support.
If you're B2C you can probably ignore that and just not support it, but if you're B2B where you're selling not to users it's very hard to get away from supporting IE11.
If your users never directly interact with you (for example you sell white-label software which gets resold) then you just can't control your end-user tech stack enough.
If you're selling to partners who sell to companies who push out logins to their customers or user base then even if <1% of users use IE 11, that becomes 5% of companies having a user with it, which becomes 30% of the partners who are asking for IE11 support.
It's one thing to turn down 1% of users it's quite another to annoy 30% of your income stream.
As long as bootstrap 4 is supported (and the legacy bootstrap 3 support suggests it will be) then this doesn't have to be a problem of course, just one more thing to be aware of.
I'm fortunate enough to be in the B2B where our customers are generally less tech inclined so we can actually say "You really shouldn't use IE, download this." and they actually do it. And our customers customer's are even less technically inclined, and they do it too.
Some even come back with feedback "Hey this other stuff works now!"
I like to think we're helping make the world a better place ;)
Granted while the leverage is nice, supporting those customers can be a bear.
Doesn’t Microsoft advise against using IE11 because of security reasons, except for critical internal applications that only support IE11? [0] It’s mind blowing to me that companies continue to use an insecure browser, to the point of insisting on it.
Why can’t vendors refuse to support IE11 on the grounds that it’s a security risk? If you reframe the problem to “IE11 is insecure,” surely customers will adapt?
I work for a relatively large B2B company and we’ve managed to convince the business to drop support for IE11 and Edge (the EdgeHTML rendering engine version). It was just a matter of pointing out the development cost and using analytics to show that very few of our users uses either browser.
Somehow the large FinTech company I work for dropped support for IE 11 and just asked employees to use Chrome. Even users still on Windows 7.
We run a few customer portals and a customer facing ticketing system. Until now I’ve never been able to rid myself of IE 11. It’s very nice. Small banks aren’t so happy.
Not to mention that if your software sends out emails with links to your application, chances are high that your client's email client (Outlook) will open the links in the default browser (which still might be IE).
So even if you can convince them to use a different browser, be prepared to tell them how to configure the browser to be the default one.
IME, the IE11 users have all been able to use another browser. We send them to version of our site that includes all the right polyfills and allows signups/browsing marketing but NOT using the main app.
When users arrive on IE11 and need to use the app they are always able to fire up chrome/Firefox/edge.
The only users with an old browser and won't/can't upgrade have had win7 + ancient Firefox.
We're mostly a voice application so with WebRTC being a requirement to our application we've completely dropped support for IE11 and Edge (pre chromium)
We've had to maintain support for Safari which has been very problematic since they initially released WebRTC support but not exactly bug free. That said it's a joy to develop for the web now without worrying about IE
I have been helping maintain and update an online fabric store. If anybody is going to be using ie11, it’s old people with old computers buying fabric for things. I think it’s still 7% of the larger market, no? I don’t see how stores can just ignore 7% of users unfortunately
Since it's open source, it sounds like companies who get 30% of their money from IE users should start giving enough back in time and money that Bootstrap does what they need. That, or look up parables on gift horses and little red hens.
Personally I feel the correct solution for ie is to have stuff polyfilled and transcompiled by the user. So js libs, you also transcompile the libraries also and provide the polyfills.
It's different for all kinds of of markets, in the markets we deal with (primary industries), our experience is, a lot of IE11 users are users with a lot of $ who have a lot of infrastructure built around older tech. The old tech keeps working fine, which is great in many ways. So, I think unless Microsoft kills it, IE11 is still the minimum for widest adoption. However, for my side projects, I just care about the evergreens.
> IE 11 is still supported by Microsoft because it is tied to Windows 10 support.
And slow to adopt banks who's check scanner software STILL depends on some ie11 feature. Edge support is coming "soon" which apparently includes the past 3 or 4 years.
Personally I’m hopeful for the day when Edge becomes default. I believe it’s still able to use the older engines for compatibility, but not having to code for Trident for default Windows users would be so nice!
Imagine a world not too far away where Credge is the only browser accessible and IE tab is available there but doesn’t open unless there’s a flag on a site to say “use IE Tab”
My company has a few SaaS apps that really only work in Chrome. I would say Chrome is a more prevalent corporate browser than IE11 at this point.
The biggest issue with IE11 from a corporate IT support perspective is that it is not cross-platform so it adds another platform to test and validate against. Most organizations have to support some level of Mac usage for software developers and executives, so it makes more sense to officially support only a single browser.
I. Rename IE11 something like "MS ActiveX Runtime For LOB Network Apps" (AXR for short) or something like "MS ActiveX Player".
II. Create an MMC console entitled "AXR Domain Manager" that identifies a list of domains that open in AXR instead of the default browser. This list is controllable via group policy and other MS management tools.
III. Modify IE where if a website not in the aforementioned list is accessed, a popup saying "This site will be opened in your default browser" appears and the link opens up in the default browser.
It would make it so much easier to explain to non-technical people that IE11 is really a legacy app engine at this point and shouldn't be used for modern website usage.
There are still companies in Europe I work with that use IE11.
Since we switched from jQuery to Vue last year, we put a friendly reminder on each page saying IE11 is not supported (since its ES6 support sucks), but the tickets still came in. Finally we installed a header on all B2B sites that pops a modal error saying please don't use IE11. The tickets stopped abruptly. I was expecting complaints, but the majority of them already have alt browsers installed, so instead of asking, in this case forcing them to use a different browser worked much better.
I wonder how many of these ancient legacy systems are content to stay on IE because everyone coddles them with support? Chicken and the egg kind of thing. Why invest the time and money to modernize if devs will bend over backwards to keep them on life support?
More likely it's because no one wants to pay to upgrade the hundreds of barely supported in-house apps their company has that only run on IE 11 in compatibility mode.
Not sure. At least in my experience, the people demanding that their apps keep working on IE11 are not the people who care about what framework we use to build the apps.
It depends on your user base. Sometimes you must coddle because the users are still high on your active user reports and not supporting them is a choice between killing off that user base or keeping them.
For instance if your business model is to sell to/support highly regulated industries or govt users you are effectively forced to support their current user base configs or lose that share of the market because the choice for them is deal with a huge change to their requirements and support (which move at a glacial rate) OR chose a different vendor for your provided service.
Especially because the ones to make that call may not know that their business apps support other web browsers. We sell some tools, which also work on IE11 but definitely on other web browsers. Do our clients know that? I wouldn't know, and wouldn't count on it.
As a provider, supporting old tech stacks sucks. They're clunky, have all kinds of warts and annoying workarounds for stuff that got improved in future versions.
As a consumer, being told my light bulbs won't work with the new fixture is a great reason to no longer work with that provider.
As a provider that knows this, I'd rather support the old tech stack right up to the point my ability to keep the lights on isn't at risk.
IE 11 legacy support is a dream compared to having to support IE 8 and lower back in the day. The JS engine on IE 9 was about 10X faster than the one on IE 8.
Don't forget the fact that some (how much ?) users visit websites with IE because it's the default browser on their entreprise setup, but admins have installed Firefox alongside for compatibility with modern websites.
So dropping IE is almost a service for them.
Source : french administration with thousands of employees.
I'm even not sure what an average experience on IE11 would be for any users.
I push as much as I can to POs / stakeholders to just disable non-critical features on IE11 and just leave the basic functionality.
I doubt anyone using IE11 likes that fact, so sounds good to give them just another reason to complain about their experience to their superiors. I will definitely never see "The product that just works on IE11" as a slogan, so being competitive in this won't be reasonable argument.
What are some good alternatives for developers who don't want to lose 2,39% (or whatever the current MSIE11 market share is) of their visitors/revenue?
Bulma claims 90% compatibility with IE11 at least. Foundation 6 seems to support IE9+.
Why aren't IE users considered more when thinking about accessibility? The best practice is to incorporate a11y accessibility standards to accommodate the small percentage of users who use screen readers and/or have color blindness/other disabilities. Why are we so quick to drop IE11 support when supporting users with disabilities is just as much work if not more? And possibly are a smaller percentage of users than IE users? You'll never read "Bootstrap stops supporting screen readers and removes aria tags in v6".
By extension, can we classify IE usage as a disability? Only half joking: I imagine a lot of current IE users are either doing it because of work or because they are technologically illiterate.
Nobody likes to support IE11 but dropping support moves Bootstrap 5 from "just use Bootstrap" to "Bootstrap has tricky pitfalls". Before someone can use Bootstrap 5 they need to be sure and confident that they don't need IE11 and never will.
IE11 was supplanted by Edge years ago. Windows 10 ships with Edge preinstalled (it comes with both, but you're not stuck with IE). Windows 7 and older are no longer supported by MS. The only in-between is Windows 8 which everyone hated so I doubt it has a huge market share, especially in enterprises which are the only ones who might be "stuck" with the browsers that come preinstalled on the OS.
Good lord, looks like I’ll have to wait a few years to use this update then. We have a decent amount of legacy browser users that need support. Wish that Bootstrap supported these still widely used browsers. Had the same problem with v4.
[+] [-] 7777fps|6 years ago|reply
If you're B2C you can probably ignore that and just not support it, but if you're B2B where you're selling not to users it's very hard to get away from supporting IE11.
If your users never directly interact with you (for example you sell white-label software which gets resold) then you just can't control your end-user tech stack enough.
If you're selling to partners who sell to companies who push out logins to their customers or user base then even if <1% of users use IE 11, that becomes 5% of companies having a user with it, which becomes 30% of the partners who are asking for IE11 support.
It's one thing to turn down 1% of users it's quite another to annoy 30% of your income stream.
As long as bootstrap 4 is supported (and the legacy bootstrap 3 support suggests it will be) then this doesn't have to be a problem of course, just one more thing to be aware of.
[+] [-] duxup|6 years ago|reply
Some even come back with feedback "Hey this other stuff works now!"
I like to think we're helping make the world a better place ;)
Granted while the leverage is nice, supporting those customers can be a bear.
[+] [-] chatmasta|6 years ago|reply
Why can’t vendors refuse to support IE11 on the grounds that it’s a security risk? If you reframe the problem to “IE11 is insecure,” surely customers will adapt?
[0] https://www.zdnet.com/article/microsoft-security-chief-ie-is...
[+] [-] fiddlerwoaroof|6 years ago|reply
[+] [-] wil421|6 years ago|reply
We run a few customer portals and a customer facing ticketing system. Until now I’ve never been able to rid myself of IE 11. It’s very nice. Small banks aren’t so happy.
[+] [-] leifg|6 years ago|reply
So even if you can convince them to use a different browser, be prepared to tell them how to configure the browser to be the default one.
[+] [-] bluedino|6 years ago|reply
[+] [-] tln|6 years ago|reply
When users arrive on IE11 and need to use the app they are always able to fire up chrome/Firefox/edge.
The only users with an old browser and won't/can't upgrade have had win7 + ancient Firefox.
[+] [-] taf2|6 years ago|reply
We've had to maintain support for Safari which has been very problematic since they initially released WebRTC support but not exactly bug free. That said it's a joy to develop for the web now without worrying about IE
[+] [-] gentleman11|6 years ago|reply
[+] [-] wpietri|6 years ago|reply
[+] [-] phyzome|6 years ago|reply
- For some websites (e.g. government) it is important not to "lose" even 1% of the potential userbase -- it's another type of accessibility
- For some websites, IE 11 usage will be considerably more than 1% in the first place
[+] [-] marcthe12|6 years ago|reply
[+] [-] keithnz|6 years ago|reply
[+] [-] MisterTea|6 years ago|reply
And slow to adopt banks who's check scanner software STILL depends on some ie11 feature. Edge support is coming "soon" which apparently includes the past 3 or 4 years.
[+] [-] munchbunny|6 years ago|reply
[+] [-] modmans2nd|6 years ago|reply
[+] [-] wayoutthere|6 years ago|reply
The biggest issue with IE11 from a corporate IT support perspective is that it is not cross-platform so it adds another platform to test and validate against. Most organizations have to support some level of Mac usage for software developers and executives, so it makes more sense to officially support only a single browser.
[+] [-] unknown|6 years ago|reply
[deleted]
[+] [-] tenebrisalietum|6 years ago|reply
I. Rename IE11 something like "MS ActiveX Runtime For LOB Network Apps" (AXR for short) or something like "MS ActiveX Player".
II. Create an MMC console entitled "AXR Domain Manager" that identifies a list of domains that open in AXR instead of the default browser. This list is controllable via group policy and other MS management tools.
III. Modify IE where if a website not in the aforementioned list is accessed, a popup saying "This site will be opened in your default browser" appears and the link opens up in the default browser.
It would make it so much easier to explain to non-technical people that IE11 is really a legacy app engine at this point and shouldn't be used for modern website usage.
[+] [-] 0xff00ffee|6 years ago|reply
Since we switched from jQuery to Vue last year, we put a friendly reminder on each page saying IE11 is not supported (since its ES6 support sucks), but the tickets still came in. Finally we installed a header on all B2B sites that pops a modal error saying please don't use IE11. The tickets stopped abruptly. I was expecting complaints, but the majority of them already have alt browsers installed, so instead of asking, in this case forcing them to use a different browser worked much better.
[+] [-] darekkay|6 years ago|reply
[1] https://stackoverflow.blog/2020/03/31/building-dark-mode-on-...
[+] [-] fortyseven|6 years ago|reply
[+] [-] beart|6 years ago|reply
[+] [-] efdee|6 years ago|reply
[+] [-] wstuartcl|6 years ago|reply
For instance if your business model is to sell to/support highly regulated industries or govt users you are effectively forced to support their current user base configs or lose that share of the market because the choice for them is deal with a huge change to their requirements and support (which move at a glacial rate) OR chose a different vendor for your provided service.
[+] [-] sebazzz|6 years ago|reply
[+] [-] mleland|6 years ago|reply
I hate supporting IE, but that has always been the appeal of bootstrap for me.
[+] [-] czechdeveloper|6 years ago|reply
But they can't really stay relevant and keep supporting IE.
[+] [-] baccredited|6 years ago|reply
[+] [-] tzs|6 years ago|reply
Of people who actually order:
[+] [-] Raed667|6 years ago|reply
During the weekend this kind of traffic drops significantly, which means to me that people using IE have to, and not choose to.
[+] [-] cfv|6 years ago|reply
As a consumer, being told my light bulbs won't work with the new fixture is a great reason to no longer work with that provider.
As a provider that knows this, I'd rather support the old tech stack right up to the point my ability to keep the lights on isn't at risk.
[+] [-] Cthulhu_|6 years ago|reply
[+] [-] jgalt212|6 years ago|reply
[+] [-] sjroot|6 years ago|reply
We don’t use Bootstrap, but hopefully this encourages the companies that do use it to usher their users to something more modern and secure.
[+] [-] maelito|6 years ago|reply
So dropping IE is almost a service for them.
Source : french administration with thousands of employees.
[+] [-] drinchev|6 years ago|reply
I push as much as I can to POs / stakeholders to just disable non-critical features on IE11 and just leave the basic functionality.
I doubt anyone using IE11 likes that fact, so sounds good to give them just another reason to complain about their experience to their superiors. I will definitely never see "The product that just works on IE11" as a slogan, so being competitive in this won't be reasonable argument.
[+] [-] lazyjones|6 years ago|reply
Bulma claims 90% compatibility with IE11 at least. Foundation 6 seems to support IE9+.
[+] [-] purerandomness|6 years ago|reply
[+] [-] Solvitieg|6 years ago|reply
Stay on Bootstrap 4. It will be supported until late 2021.
[+] [-] tln|6 years ago|reply
We build an IE compatible marketing and sign up flow, so I may only be seeing the motivated users' behavior
[+] [-] StreamBright|6 years ago|reply
[+] [-] rado|6 years ago|reply
[+] [-] ativzzz|6 years ago|reply
By extension, can we classify IE usage as a disability? Only half joking: I imagine a lot of current IE users are either doing it because of work or because they are technologically illiterate.
[+] [-] bfred_it|6 years ago|reply
[+] [-] jmull|6 years ago|reply
Nobody likes to support IE11 but dropping support moves Bootstrap 5 from "just use Bootstrap" to "Bootstrap has tricky pitfalls". Before someone can use Bootstrap 5 they need to be sure and confident that they don't need IE11 and never will.
[+] [-] _bxg1|6 years ago|reply
[+] [-] k__|6 years ago|reply
I used it excessively 6 years ago. Then the v4 took an eternity to release and I already switched to different solutions.
I would have thought that people that are still using it are doing so because of legacy support.
[+] [-] websitescenes|6 years ago|reply