Bruno Bernardino

@MaKleSoft I've fixed the conflicts here, if you could please review it! :heart:

@MaKleSoft ready for review again, and BTW, with the new login email notification I added yesterday, this will fully close #346

@MaKleSoft let me know if you'd like me to fix this.

@MaKleSoft is this still relevant?

Have you seen this happen with Beta? I haven't _unless_ I've previously selected all items before. In that case I get taken there instead of matching items.

More information: - https://docs.microsoft.com/en-us/microsoft-edge/extensions-chromium/publish/publish-extension - https://developer.microsoft.com/en-us/microsoft-edge/extensions/

@MaKleSoft I've just finished going through their documentation and the signed and unpacked extension both work in Edge without any changes required (I'll just push some documentation tweaks). Here's what...

Ok, now we're waiting for a reply on their end because the ZIP file (even without any code, just basic `manifest.json`, `icon.png`, and `popup.html`) fails to be parsed.

They've fixed it on their end and I was able to upload the CI-built beta extension. This is ready to go now, we just need to re-upload once we release...

Unfortunately we just missed the window to release our extension there as they stopped supporting manifest v2 a few days ago, so we'll need to migrate the extension to v3...