displayDialogAsync() with the setting displayInIframe: true, on IE11 Word Online should successfully open a dialog window just like it does on all other browsers including Chrome and Edge.
On IE11, displayDialogAsync() returns a failed status with the error message:
"The domain of the URL is not included in the AppDomains element in the manifest, and is not subdomain of source location"
This happens after the domain of the URL passed to displayDialogAsync() is added as an AppDomain element in the manifest file.
Additional notes:
This is blocking our Office Store Add-in submission.
@qinliuMSFT - I can't seem to find you in the list of assignees.
The issue related to Dialog API, @lliu113 will help take a look.
@JamesBigChange - thanks for reporting this! Are you able to provide the manifest for your add-in? We have restrictions around the domain that can be opened in the dialog, and it's possible it's throwing an error from a false positive. The manifest will help us repro the issue.
Thanks!
Lillian
@JamesBigChange - thanks for reporting this! Are you able to provide the manifest for your add-in? We have restrictions around the domain that can be opened in the dialog, and it's possible it's throwing an error from a false positive. The manifest will help us repro the issue.
Thanks!
Lillian
Thanks @lliu113, I have emailed you our manifest. Please confirm that it was received.
@JamesBigChange - manifest was received, thank you! What's the domain of the dialog you're trying to launch? And this is occurring just in IE11, correct? All the other browsers are working correctly?
@lliu113 thank you. The domain for the dialog is: https://clients.bigchange.com
Yes that's correct - it works in all browsers except IE11.
@JamesBigChange - Unfortunately I can't seem to get your add-in to side-load (it's giving me a blank page in the taskpane), and I'm unable to repro this with another add-in. The dialog is launching correctly in IE11 for me, when the domain is one specified under AppDomain.
Let me circle this internally and see if this is a known bug. Will revert back soon - thanks!
@JamesBigChange - quick update, we were able to repro this issue successfully. The manifest was a huge help, thank you for providing that! We are currently investigating the root cause, which may take some time. Will update when we know more, thanks!
@JamesBigChange - the fix is checked in, and starting to roll out
@lliu113 thank you. Do you have an estimate for the rollout time?
@JamesBigChange - unfortunately no estimate as of yet, but will update next week on status. Thanks for your patience!
@JamesBigChange - good news, this is now in production! Please test and let us know whether this is working for you.