-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Proposal: IE 11 Support #6423
Comments
As someone who works on an application for the healthcare sector where IE 11 will be around a long time I would love to see support implemented. Kudos for considering this rather then just dropping plans because MS declared IE 11 EOL. :) |
There is still a massive amount of computers on IE 11 and while IT departments exist this will probably remain the case, so this would be very good to have. |
Hope Safari will get higher priority as it definitely not going to disappear and actually is new IE 😁 |
@levenleven thats weird cause I never have Safari behaviour deviate from Chrome. shouldn’t IE11 be more important because of the much higher risk of deviation (such as use of polyfills)? |
@jpike88 jokes aside, both are important. I'm just hoping MS will try to kill IE faster because Edge should have compatability mode. Also more and more non enterprise projects just drop IE support |
This comment has been minimized.
This comment has been minimized.
We actually been using Cypress for more than a year and waiting for IE11 support, because we have a lot of customers in Japan, who are using IE11. Those clients are very important to us. So if Cypress doesn't plan to support IE11, we will have to switch to some other framework. |
@vladnauto Feel free to donate engineers or money to the effort |
I'm a maintainer of Mocha, and sometimes I'm dreaming of a life without IE11. |
this is a must have IE11 support, as most of financial domains still have IE11 as primary browser |
@juergba I don't think it's realistic for a project as large as Mocha to drop support for IE11 in the near term. It also goes with out saying that major corporations around the world have a heavy dependency on IE11. Edge failed to gain traction and "new Edge" is still extremely new. Mocha dropping support for IE11 in the near term would seriously hinder a lot of developers and projects. |
IE11 isn't going away for a long, long long time. |
Hey everyone, please try to keep the discussion focused on your personal or company needs for Cypress supporting IE11. We don't need a debate in general about IE11. We'd like to hear directly from people who use Cypress and want testing for the IE11 browser so that we can better evaluate our roadmap. @juergba Thanks for sharing. Evaluating our dependencies support for IE11 will definitely factor into our decision. |
Hi, we work for big clients, mainly in french finance & insurance companies. Mixpanel stats show ~40% of IE 11 as of today, which is steady for the last few years. I suppose their IT stick on this browser as long as possible, and we will certainly see a big change when they change all their software at once ; but for now, it's the single most used browser by our customers. Second comes Chrome, but with a lot of different version, sometimes pretty outdated. So, thanks for thinking about non-tech companies :) Looking forward to using Cypress with IE 11. |
+1 to this idea, some of us are still supporting IE11 as browser and we need to test againt it, thanks! |
We also support a lot of corporate clients that are still using IE11. The majority of our traffic comes from IE11, so Cypress adding support for it would be a big help. |
In case it's easier than actual IE11 support, having Chromium Edge in the IE11 mode would already help. |
Hi @jennifer-shehane , Thanks for the clarification. In our organisation (50k+ users) IE11 is still the default browser. Many legacy applications do not support Chrome yet. I have been trying to adopt within the organisation and everyone can clearly see the benefits of using it over other frameworks but at the end of the day if it's not browser agnostic it makes the conversation very difficult. On that note great work on supporting Firefox and the new Chromium based Edge. I really hope you reconsider this and support IE11 in the near future or sadly we will have to look for an alternative solution. |
My customer is using IE11 and their organization it is still heavily used |
Like others have said, as someone in the healthcare space, IE11 support is a must-have. We're working in large networks of hospitals that all require our application work in IE11. |
+1 Legacy systems as most of banking domains are still on IE11 |
We're In exactly the same boat as @admah and others:
Healthcare in particular is an issue and not going to change any time soon because we're dealing with large organizations and inflexible policies. |
Would love to see this. My company has a significant number of clients still on IE11. |
Our projects are with the government of various countries and more than 8o% of them are on IE. We really want to switch to cypress and waiting for IE compatible version. |
Hey, is there an update on this since Feb 2020? My co is also considering migrating off of Cypress because we'll need IE11 support in the near-future. |
There is some work we are doing on support Safari. There is no movement on supporting IE11 for now |
IE 11 support is still relevant for my organisation - we support modern chrome/firefox/edge and Safari version 9+ and IE 11. |
Where I work all departments still use IE for secure reasons |
IE 11 support is actually going to become more important for us after end-of-life. Because development will no longer naturally check that changes work in IE, we'll need to rely on something in CI to flag issues. |
@jennifer-shehane Please update whether IE 11 got prioritized and any other details. I'm starting to used Cypress in my React app and eagerly looking for more browser support, and IE 11 is of the most needed. As a major chunk of my customers are on IE11 :( |
+1 for IE11 support! |
I would also like to test in IE (at least IE 11). |
IE11 testing is needed in my organization. We have been using Cypress for the past 2 years |
The organisation I work for is currently looking at using Cypress for E2E testing, but lack of IE11 support is currently the biggest factor pushing us towards other options such as webdriver io or TestCafe. Our applications are primarily in the healthcare sector where many users are obliged to use IE11 still and this is unlikely to change any time soon. |
I'm glad so many others are also expressing a need for this feature in but please just thumbs up the initial post. Thanks |
+1 , and we still need to maintain it for a long time after EOL so this update would greatly improve our ability to catch issues. Thanks for all the great work you do! |
+1, this would eliminate the need for manual testing just for IE11 |
Are there any updates on the ie11 support or any workarounds? |
@Pedro-Puga |
+1 for IE11 support |
My company works in Healthcare with Epic and Cerner (Which run in 90%) of US hospitals. Both of these software host their apps in IE11. This unfortunate browser is not going away anytime soon |
+1 for IE11 support! I also work for a Healthcare company and most of our users still use IE. Thanks for considering this! |
I also work for a Healthcare company and we have been thinking about using Cypress in our new project. But without the IE11 support, I cannot have a conversation about benefits of adopting this great tool! Please consider this request. Hoping to see the IE browser support soon. Thanks! |
+1 for IE11 support |
We are testing in IE and would be great if Cypress will support that browser. |
As a financial technology firm that needs to support other business' hardware, IE support would be extremely useful. We can control what our direct customers use to access our sites, but we cannot force our business partners to update their corporate browsers. |
For our customers that support Windows users, not having support for IE 11 is a deal-breaker. We have used Cypress for many things in the past and enjoyed it, however for those customers we are having to identify a different solution as more than 50% of their users are still on IE11 sadly. |
Support for InternetExplorer has Ended officially by Microsoft. IE has (finally) reached end of life and imho this issue can be closed. |
@tux-rampage That is not accurate. You are referring to support under mainline consumer versions of Windows 10 only. Windows 7 ESU, 8.1, and 10 Enterprise channels end next year and LTSC for 10/Server/IOT go until Jan 2029. IE Mode in Edge is a whole different story. |
@sscotth Thanks for the clarification I was not aware of. So it seems we do not get rid of that Zombie-Browser 😞 |
We're closing this issue since IE11 is retried and officially out of support as noted in this blog post from Microsoft. If you have a case where you would like to support testing for IE Mode in Edge or some other case surrounding IE support, we suggest opening a new issue for tracking so that we can better prioritize that work separate from IE 11 support outright (which this issue was tracking). |
Objective
Add support for running Cypress tests within the IE 11 web browser.
The text was updated successfully, but these errors were encountered: