Search Bar Queries in Microsoft Edge are Blocked

[stephendt]

Firstly, yes I know I am using Edge instead of Chrome, but I have been using this for over a year with no issues. Unfortunately, as of yesterday I am having a few issues running this extension in Microsoft Edge. When I try to do a search from the search bar, I will get a message that says:

lllggmgeiphnciplalhefnbpddbadfdi is blocked

This page has been blocked by Microsoft Edge
ERR_BLOCKED_BY_CLIENT

However, if I use the address bar, the search works fine. Not sure if this is an issue with the extension or Edge, but it certainly is annoying.

[HumanGamer]

I'm having this issue too. It also asked for a new permission to block web pages recently, not sure if that's related.

[HumanGamer]

So I think the issue is the recent changes to the extension. How can I use an older version? The extension worked fine until now.

[HumanGamer]

I manually built d304d88 and installed it as an unpacked extension and it worked.

Steps:

1. install node
2. install grunt
3. clone the repo and in the repo folder, run npm install followed by grunt build-chrome
4. the unpacked extension is now in the dest folder
5. copy the dest folder somewhere permanent (i put it in D:\Extensions\Chrometana Pro (old)
6. set edge to developer mode and load an unpacked extension passing the folder you copied.

Here is the built files for anyone that wants it: https://mega.nz/file/x0NmyAqb#hTSIcYevgvjHPBzSt_DD3oI2eeKgR5CHJy6KKIsEJ8k

(note: i tried to upload it to the message directly but github was complaining that it was an invalid file type and to use a zip...even though it is a zip? So I put it on mega. I have mega pro so the file won't be going anywhere unless I cancel my pro subscription)

[MarcGuiselin]

It also asked for a new permission to block web pages recently, not sure if that's related.

I switched to the declarativeNetRequest extension api since google is phasing out support for v2 extensions and the webRequest api. Unfortunately this change required an update to permissions even though "blocking" is never used.

The behavior of this api should be the exact same between chrome and edge. It shouldn't be blocking anything, and redirects correctly in chrome.

I'll investigate and look for a fix tomorrow.

[MarcGuiselin]

Yup, I can confirm edge has a strange behavior where it blocks redirects to extension pages. The current workaround is to redirect all bing searches directly to the search engine of choice, this has a few compromises listed in #16.

[MarcGuiselin]

This issue has been fixed in v 2.2