Type of issue

Outdated article

Feedback

Issue:

The current guidance provides workarounds for running Angular Office Add-ins in the Trident (IE11) webview by manipulating window.history and recommending hash-based routing. However, this is now out of date for all modern Angular versions (Angular 12 and higher).

• Angular 12 dropped IE11 support entirely. As stated in the official Angular browser support guide and Angular deprecation RFC, IE11 is no longer supported in Angular 12+—the CLI, build tools, and most dependencies cannot produce code compatible with IE11, regardless of polyfills or workarounds.
• Any attempts to use Angular 12+ with the Trident webview in Office clients (e.g., Outlook 2016/2019) will fail. This guidance may mislead developers into attempting an unsupported configuration.

Request:

• Please update the documentation to clarify that these workarounds are only valid up to Angular 11.
• Add a clear warning that Angular 12 and later versions do NOT support IE11 or the Trident webview, and Office Add-ins using Angular 12+ require environments with modern webview support (such as WebView2/Edge).
• You may wish to point developers to browser support resources and encourage migration to up-to-date Office clients and browser engines for Angular add-in development.

Page URL

https://learn.microsoft.com/en-us/office/dev/add-ins/develop/add-ins-with-angular2#support-the-trident-webview-control

Content source URL

https://github.com/OfficeDev/office-js-docs-pr/blob/main/docs/develop/add-ins-with-angular2.md

Author

@o365devx

Document Id

5fcb4dc0-275a-a365-b0ac-3f97f2cd40cb

Platform Id

b69a7a53-8d8e-ce31-1560-d694f658e632