Open joerivv opened 7 months ago
@SiruiSun-MSFT would you please help to take a look?
@SiruiSun-MSFT Did you have a chance to look at this issue?
Hi @joerivv, Sorry for the late response. Since our team is not the owner of this feature, we have already internal connected with partner team. If there is some update, will reply here for your information. Thanks for your patience!
@SiruiSun-MSFT Has there been a response from the partner team yet? Or is there perhaps someone we can contact directly? I am asking because while the issue may seem a silly edge case, this roadblock is actually the only thing stopping us from deploying and marketing our add-in, proving to us and showcasing to our clients the future viability of OfficeJS development. Any update much appreciated! Thanks!
Unfortunately, we have not received an effective reply from the partner team yet. We have already sent another email to seek for help. If there is any updates, we will reply here ASAP.
Hey @joerivv, our partner team has taken over and is looking into this issue. Thanks for your patience!
Hi @joerivv, this should have been fixed. Could you help verify? Thanks!
When a button links to an external (standalone) tool via a custom-defined protocol (so instead of https://, something like pxl-risk-finder://), Excel comes up with this message:
There are two Cancel buttons, and the "Always remember" checkbox does not work. If the add-in also features a taskpane (side panel), and if this taskpane has been opened at least once, the warning appears in the taskpane instead:
Note that if you close the taskpane and then follow a link to a custom protocol (by clicking a CommandButton in the ribbon, say), the warning appears in a now invisible taskpane (!).
In the taskpane the "Always remember" checkbox works as expected. However, if you accidentally click “Cancel” after you check “Always remember”, there seems to be no way to get the question again (not even restarting your computer or reinstalling the Add-in works). At that point, links to external tools are permanently broken.
Your Environment
Expected behavior
A predictable way to warn users about links to custom protocols, with working controls. Most importantly: a way to define trusted protocols (or disable the warning altogether) in the manifest or through the JavaScript API.
Current behavior
Inconsistent warnings, broken controls (see above), no way to undo a decision after ticking "Always remember", and no way for developers to predefine which protocols can be trusted.
Steps to reproduce
Without a taskpane:
window.location = 'test://';
will do)With a taskpane:
Office.addin.showAsTaskpane()
should do it)Context
For rollouts in large organizations, it's not ideal that end users have to go through these steps for every protocol. Especially in our case, where the protocols are known to be safe and present, it'd be ideal if this warning could be repressed by us (the developers) or else at least by an admin.