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
{{ message }}
This repository has been archived by the owner on Jun 21, 2020. It is now read-only.
This doesn't work in IE11. It says "widget cannot load" and then "Promise is undefined". It can be fixed by installing es6-promise and adding import "es6-promise/auto"; to the top of various .ts files. Sorry I can't submit a PR; I'm waiting for my organization to finish some paper work that would allow me to do that without getting fired.
Also, there are missing html content types in your vss-extension.json which prevents the page from displaying in any browser (in on-prem TFS2017U3, anyway) if anyone tries to rebuild/redeploy from your source. This seems to be true for all (or almost all?) extensions created by Microsoft or by ms-devops or by ALM Rangers.
Not supporting Microsoft Internet Explorer is also a seemingly universal shortcoming of Microsoft web extensions.
The text was updated successfully, but these errors were encountered:
I'm sorry you ran into this issue. As displayed on the Marketplace page this is a known issue:
Until a Promise Polyfill hotfix is added to the web platform of TFS on-prem, this extension is not supported with Internet Explorer (IE) 11.0.
Can you please open a new issue for the missing HTML content types? I can build and deploy the extension without any issues so I'm not sure what you're running into.
For now, I'm closing this issue and I hope you'll open a new one with more detail for the missing content types.
This doesn't work in IE11. It says "widget cannot load" and then "Promise is undefined". It can be fixed by installing es6-promise and adding
import "es6-promise/auto";
to the top of various .ts files. Sorry I can't submit a PR; I'm waiting for my organization to finish some paper work that would allow me to do that without getting fired.Also, there are missing html content types in your
vss-extension.json
which prevents the page from displaying in any browser (in on-prem TFS2017U3, anyway) if anyone tries to rebuild/redeploy from your source. This seems to be true for all (or almost all?) extensions created by Microsoft or by ms-devops or by ALM Rangers.Not supporting Microsoft Internet Explorer is also a seemingly universal shortcoming of Microsoft web extensions.
The text was updated successfully, but these errors were encountered: