OfficeDev / OfficeDev/office-js

Office.context.ui.displayDialogAsync popup dialog forcibly ignored in Edge Outlook calendar

Open
#6,000 7 comments 0 reactions 1 assignee View on GitHub

@exextoc is already working on this.

Since Aug 12, 2025.

Area: Outlook Needs: attention :wave: Possible-Solution Similar-Issue
Dominant language
JavaScript
Stars
845
Forks
124
Avg merge
3d 17h
Merged PRs (30d)
1

Description

Provide required information needed to triage your issue

Your Environment

  • Platform [PC desktop, Mac, iOS, Office on the web]: PC desktop
  • Host [Excel, Word, PowerPoint, etc.]: Outlook (Edge web version)
  • Office version number: ______
  • Operating System: Windows
  • Browser (if using Office on the web): Microsoft Edge

Expected behavior

When using Office.context.ui.displayDialogAsync(url, {height: h_p, width: w_p}, displayDialogAsyncCallback); to display a popup confirmation dialog, it should appear normally and allow authentication to complete successfully.

Current behavior

In Edge Outlook calendar, when attempting to display a popup dialog using the above API, the dialog is forcibly ignored and authentication fails. This issue does not occur in classic Outlook client or new Outlook client.

Steps to reproduce

  1. Open Outlook in Edge browser
  2. Navigate to calendar view
  3. Execute an add-in that uses Office.context.ui.displayDialogAsync to display a popup dialog
  4. Dialog is ignored and does not appear

Link to live example(s)




Provide additional details




Context

In Outlook add-ins that require authentication flow, users cannot complete authentication because dialogs are not displayed only in Edge Outlook environment. This prevents users from properly utilizing the add-in functionality in Edge environments.

Useful logs

  • Console errors
  • Screenshots
  • Test file (if only happens on a particular file)

Thank you for taking the time to report an issue. Our triage team will respond to you in less than 72 hours. Normally, response time is <10 hours Monday through Friday. We do not triage on weekends.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.