Is it possible to support IE 10 & 11 please? about playwright

[aslushnikov]

No, there are no plans to support IE10/IE11. This would be a huge engineering effort and should be very well justified.

I'll close this for now, but feel free to share your thoughts / upvote the bug to vouch for the need of this.

[Vandivier]

Just a comment - Edge has IE11 mode which might be a way to hack in some IE11 e2e support.
Related Cypress discussion: cypress-io/cypress#6423

[weyert]

That would be the dream if it could support IE11 or Edge. I have been wondering if chromeless MSHTML.dll is possible on those Windows Core docker images. My gut feeling says no but would be cool

[nathanboktae]

Supporting IE is a whole another thing. It can't run headless, which means it needs a GUI, and a graphics card. If you have to support IE, you should probably stick with Selenium & WebDriver, as flakey as it is. That's just the reality. Or push your product and company to not support it and call out the costs it incurs.

[JoelEinbinder]

I'm not that familiar with the world of IE. Is your main concern that javascript runs correctly and html renders correctly in the engine? Or do you need to test activex and other legacy things that only IE supports?

[nagaozen]

That would be the dream if it could support IE11 or Edge. I have been wondering if chromeless MSHTML.dll is possible on those Windows Core docker images. My gut feeling says no but would be cool

I built a docker image sometime ago based on the windows base os 1809 image and it have mshtml.dll working on it https://hub.docker.com/r/nagaozen/asp-docker. I've also requested a review to add the fod stuff on windows server core images: https://github.com/MicrosoftDocs/windows-insider/issues/56. If you guys also thinks it useful, let's pump the issue up.

[aaronamm]

Hi @JoelEinbinder. Thanks for your comment.

The main functionalities that we want test on IE are:

• Navigation web page
• Interact with DOM.e.g. click, send text, select option, focus, waiting for amount of time, waiting for DOM loaded.
• Get JavaScript errors during testing.
• Screenshot is optional but it is useful for testing if layout rendering is correct or taking a screenshot when testing fail. FYI, puppeteer-ie do not render screenshot image correctly. A website I tested renders correctly on IE but a screenshot shows ugly layout.
• We don't test ActiveX or other legacy stuff.
• Main usages are automated testing like users interact with a website on IE browser.

Thanks.

[weyert]

I would already be delighted if you could render and screenshot things in ease :)

[flash-me]

Even after the end of support for Windows 7 (except extended paid one), people still struggle with IE.

Every single project I know that had to support IE ended up with huge mess in their codebase due to IE specific hacks, and exponential high efforts wasting nerve-racking time.
Guys, just consider the security faults by using IE.
Crazy. just crazy.