Office Add-ins should run in Edge, not IE11
At the moment Word runs Add-ins in IE11
IE11 doesnt support ES2016, and is therefore much harder to develop for than all of the other newer browsers (Safari, Chrome, Edge).
Word should run Add-ins in Edge

This is now GA. Please note that has both Office and Windows requirements.
See details here: https://developer.microsoft.com/en-us/office/blogs/microsoft-edge-webview-for-office-add-ins/
21 comments
-
Javlon Juraev commented
Why not give a developer a choice which browser to use for web add-ins - stop forcing your browser on users, guys
-
Michał commented
When Chromium-based Edge is released, will add-ins instantly use it instead of Edge-HTML?
-
Anonymous commented
So it seems this is not in preview anymore, but is in production now?!
I have an add-in which is now being loaded using Edge and I have no idea on how to debug this!? I've been searching for hours now. Only the IEChooser.exe is mentioned everywhere.
Also, there seems to be a way to force using IE instead of Edge (Microsoft's Insights add-in is still using IE). But unfortunately I'm unable to find any documentation about this.
-
Christian Kütbach commented
Is this the EdgeHtml-Edge or the Chromium-Edge?
-
David Nguyen commented
According to the documentation here https://docs.microsoft.com/en-us/office/dev/add-ins/concepts/web-viewers-used-by-office-web-add-ins, the feature will be available since Windows >= 1903 and Office >= 16.0.11629
-
Ali Koc commented
any updates? how about provide a link to an issue tracker or something so we can see what you are doing since July.
-
Anonymous commented
Any updates?
-
Siyit commented
any progress on this new feature?
-
Guilherme Piccin commented
Looking forward to ETA on using Edge as the engine for the add-ins.
Also, by any chance would be possible to tune the add-ins in to use Chrome engine rather than IE/Edge's?
thanks
-
dieter commented
I'm really frustrated now, nearly all libraries are using ES2016 nowadays…..
-
Dan Moorehead commented
Office Developer Team, can you please provide any kind of ETA as to when we might be able to begin use of Edge-based renderer and ECMAScript 6 instead of Internet Explorer 11 with new Office.js JavaScript-based Office add-ins?
There was just a major news article released where Microsoft calls IE "a compatibility solution, not a browser" (https://www.theverge.com/2019/2/8/18216767/microsoft-internet-explorer-warning-compatibility-solution), making this IMO even further a priority that Microsoft itself also moves away from it for its own internals, and removes the requirement that new development (like with Office JavaScript-based Add-ins) target IE11 exclusively.
Edge replaced IE11 4 years ago, and IE11 lacks EC16 support, even for basics like classes, meaning the new Office.js lacks support for clean object-oriented programming (short of transpiling from TypeScript), as well as other ECMAScript 2015 features, and basics like variables in CSS. Considering that, I believe this will be a really helpful enhancement.
Thanks,
Dan--
Dan Moorehead
● PowerExcel AI (http://PowerExcel.net) – AI generated Power Query, Pivot Tables, Tables, Named Ranges, Slicers with Merge/Split/Transform Tools & install-free Power Formula & Dynamic Array functions
● CrushErrors AI (https://CrushErrors.com) – Excel Data Prep AI, Analytics & Pivot Reporting Cloud Platform
● PowerAccess (https://PowerAccess.net) – All-in-One Toolset & Framework for Microsoft Access -
Dave Hoff commented
Also anxiously awaiting Edge support over IE11
-
arash commented
any updates on this????
-
Michael Coxon commented
Considering that many organisations still run Windows 7 and Edge is not supported in Windows 7, will these clients still run Office Add-ins in IE11? If so - would a better approach to this issue be to embed a better browser engine in Office so that everyone will have the same experience and the developers won't have to jump through the same old IE hoops?
-
Raed Alahmad commented
Outlook Apps has frontend limitations because of ES6+ on IE11. it would be much better to switch to Edge.
-
Anonymous commented
Additionally Save as web also should considering save for Edge HTML 5 above IE 6 and above
-
Brett McKenzie commented
Will this only be in Win10? I assume those on Windows 7/8/8.1 will still be running IE.
-
Christian Roy commented
It would also be nice to replace Excel Mac browser with something that support ES6.
-
Joshua Jolley commented
Versions of webpack-dev-server after 2.7.1 don't support IE11, so switching from IE11 to Edge will help developers using common build tools like @angular/cli. Please prioritize this!
-
Fergus McDowall commented
Thats great! If I could just add an extra suggestion for awesomeness: make sure that edge's "developer tools/js debugger" is available when running add-ins in Word