question about IE9 support about roadmap HOT 14 CLOSED

Internet Explorer is not an evergreen browser, it doesn't get automatic updates and it's not maintained for new features, only security and bug fixes (which is also necessary to be an evergreen browser). Edge is the evergreen browser

@FranckFreiburger If I'm not mistaken, the answer is yes, but both versions (2 and 2-next) will be maintained in parallel so v2 will still support IE9

from roadmap.

I think you misunderstand what @posva said: the next version will:

• have no breaking API changes with 2.*
• will be developed alongside 2., so they will have feature parity.

So if you have to support IE, you use 2.*, and if you don't, you use 2.*-next

from roadmap.

In ok this context however, it means all browsers supporting ES6 proxies, which means no version of IE will be supported by 2.x-next

from roadmap.

Quote from StackOverflow:

The latest versions of Chrome, Firefox, Internet Explorer, and Safari are evergreen browsers, i.e. they automatically update themselves silently without prompting the user. For Internet Explorer, most people consider this to mean IE10+.

from roadmap.

For accessibility it would be nice to still support IE11. Most windows users who rely on screen readers (or other AT that need the accessibility tree) use JAWS + IE11 still. Last I've heard Edge isn't quite there yet.

Food for thought :)

from roadmap.

No that's my point. I really hope 2.x-next doesn't leave out everyone that need to use AT

from roadmap.

@Robdel12 that's not possible, IE11 doesn't support full ES2015.

from roadmap.

Hm, is transpiling not an option?

Edit: I see now. So 2.x-next will be maintained along 2.x for the entire time (until 3.x)? My worry is people will unknowingly pick 2.x-next not knowing about that trade off.

from roadmap.

@Robdel12 that's something we will obviously communicate very clearly when releasing it.

from roadmap.

from roadmap.

Hm, is transpiling not an option?

ES6Peoxies can't be polyfilled, no (and transpilation wouldn't apply here because it's not about new syntax but a new type).

from roadmap.

@posva Right. That doesn't mean it worked with JAWS at the time (I know, a11y AT combos suck).

Thankfully as of this September JAWS 18.0.4 kind of supports edge now, but with caveats:

To use JAWS with Edge, you must be running the Windows 10 Creators update (version 1703) or later. While there are still several JAWS features that are not available in Edge such as selecting and copying using the Virtual Cursor, PlaceMarkers, Smart Navigation, Flexible Web, and domain-specific settings, we have made the overall experience of navigating pages in Edge using both speech and braille as similar as possible to working in Internet Explorer, Chrome, or Firefox. As we continue to work with Microsoft to improve the Edge experience, future JAWS updates will include greater functionality. Edge support is also available in the new JAWS 2018.

Edge support is turned off by default in JAWS 18. This is because support for Microsoft Edge depends on some emerging technologies, which we continue to fine-tune in close collaboration with Microsoft.

From: https://www.freedomscientific.com/downloads/JAWS/JAWSWhatsNew (cmd + f "edge" since I can't link the heading)

Edit: also, sorry, didn't mean to blow this up.

from roadmap.

Closing since I think the original question has been answered :)

from roadmap.

yes absolutely, thanks.

from roadmap.