You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Controlled end-to-end validation requested by the repository owner. This is a synthetic scenario, not a confirmed product defect. Please keep this issue identifiable as a validation artifact rather than citing it as evidence for unrelated issues.
Scenario and Question
An initialized @microsoft/teams-js 2.57.0 tab runs in Outlook on the web. dialog.isSupported() returns false, but our code ignores it and calls dialog.url.open(), which fails as unsupported. We enabled the button based only on the host name. Is this unsupported call a TeamsJS bug? Does upgrading the package guarantee the host will implement the capability?
Thank you for reporting this issue. Here is an AI-generated initial response:
Classification: Not a bug — in the reported scenario, the tab calls dialog.url.open() after dialog.isSupported() returns false. TeamsJS documents that unsupported API calls fail; the button should not be enabled from the host name alone.
Microsoft’s TeamsJS guidance says to gate functionality with isSupported(), not the host name. Upgrading @microsoft/teams-js does not guarantee that a host implements a capability.
The capability matrix lists URL dialogs for Outlook on the web, but cautions that support can vary and runtime checks take precedence. It does not establish why this scenario returns false.
What to do now:
Disable the button when dialog.url.isSupported() is false; check again before calling dialog.url.open().
If this occurs outside the synthetic scenario, provide the Outlook/browser version, manifest, and minimal reproduction to investigate the unexpected false result.
Useful links:
No sufficiently relevant related issue found in the searched repos.
Activity
atktroubleshootingapp commentedon Sep 28, 2026
👋 Hi @Alive-Fish,
Thank you for reporting this issue. Here is an AI-generated initial response:
Classification: Not a bug — in the reported scenario, the tab calls
dialog.url.open()afterdialog.isSupported()returnsfalse. TeamsJS documents that unsupported API calls fail; the button should not be enabled from the host name alone.isSupported(), not the host name. Upgrading@microsoft/teams-jsdoes not guarantee that a host implements a capability.false.What to do now:
dialog.url.isSupported()is false; check again before callingdialog.url.open().falseresult.Useful links:
dialog.urlAPI reference