To enable Edge to load StashPop the following changes had to be made:
Update the manifest to include the author key and fix the default_icon value to be a dictionary as specified in the Chrome extension manifest spec.
Edge exposes extension functionality through the browser object instead of the chrome object, so in cases where chrome doesn't exist and browser does, the functionality is mirrored.
Edge doesn't yet support extension settings so a defaultSettings object was created with the same values found in options.js and if no settings are found, the defaults are used as a fallback.
Known limitations:
The permissions API is currently under consideration and as such isn't currently supported, so attempts by StashPop to display Jenkins test failure data inline fail, although the Create Issue buttons, etc. work as expected.
dpoeschl
commented
8 years ago
To enable Edge to load StashPop the following changes had to be made:
authorkey and fix thedefault_iconvalue to be a dictionary as specified in the Chrome extension manifest spec.browserobject instead of thechromeobject, so in cases wherechromedoesn't exist andbrowserdoes, the functionality is mirrored.defaultSettingsobject was created with the same values found inoptions.jsand if no settings are found, the defaults are used as a fallback.Known limitations:
permissionsAPI is currently under consideration and as such isn't currently supported, so attempts by StashPop to display Jenkins test failure data inline fail, although theCreate Issuebuttons, etc. work as expected.