Feedback by UserVoice

I suggest you ...

← Feature Requests and Feedback

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

353 votes
Vote
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
Fergus McDowall shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

20 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Michał commented  ·   ·  Flag as inappropriate

    When Chromium-based Edge is released, will add-ins instantly use it instead of Edge-HTML?

  • Anonymous commented  ·   ·  Flag as inappropriate

    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.

  • Ali Koc commented  ·   ·  Flag as inappropriate

    any updates? how about provide a link to an issue tracker or something so we can see what you are doing since July.

  • Guilherme Piccin commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    I'm really frustrated now, nearly all libraries are using ES2016 nowadays…..

  • Dan Moorehead commented  ·   ·  Flag as inappropriate

    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

  • Michael Coxon commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    Outlook Apps has frontend limitations because of ES6+ on IE11. it would be much better to switch to Edge.

  • Anonymous commented  ·   ·  Flag as inappropriate

    Additionally Save as web also should considering save for Edge HTML 5 above IE 6 and above

  • Joshua Jolley commented  ·   ·  Flag as inappropriate

    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  ·   ·  Flag as inappropriate

    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

Feature Requests and Feedback: Add-in: Word

Categories

Feedback and Knowledge Base

(thinking…)