Yes, Google has removed Open With from the Chrome Web Store

[darktrojan]

… and I don't intend to put it back.

Google have made listing on the Chrome Web Store a gigantic waste of time, even moreso than it was when I first listed. I am sick of their bullshit and I don't intend to comply with their new policies.

Sorry if this affects you.

[tuwulin365]

Google Store hasn't updated for a long time, so why not just provide CRX files?

[robbely]

Chrome (and edge) is now also blocking the extension after installing it. Any workarounds?

[betamanx]

As a Vivaldi user it does affect me and I really use that extension a lot on Windows. I tried installing from the crx/developer mode but it didn't really work, errors and the python would not launch the browsers, it's crippled when installed locally. The webstore extension still works but is disabled a few seconds after launch so I have to enable it everytime it tries to 'update'. I do wish you change your mind and if there's something we can do to help, like take the webstore upload and verfication off your hands.. I'm willing to help.

[defaultxr]

For Vivaldi, it seems the following line may need to be added to open_with_linux.py:

                                        'chrome-extension://enagnhbblbolkolafgdknnoiahlbgbla/',  # Vivaldi

I added it as part of the browser_manifest['allowed_origins'] list, after the line for Opera. After that, I ran ./open_with_linux.py install again and tried "Test installation" in the Open With options page, and got Found version 7.2.6 at /path/to/​open_with_linux.py. Then I added a "browser" in the Open With options, and saw it in the context menu, and was able to open links with it just as I was able to with the Chrome Web Store version.

If that doesn't work for you, let me know.

P.S. Fuck Google.

[betamanx]

Thanks defaultx, it didn't work with windows.. i added the line to open_with_windows.py under allowed origins. I think the problem with Windows is the locally deployed extension. The webstore extension which I have its files(manifest etc) works...

I think it's a security issue between windows and local installed extensions when they try to invoke external commands. Normal extensions that do not try to launch anything outside the browserwill work when installed from developer mode.

I know because I tested with other kinds of open with extensions that are still on the store(for now), when installed from google's webstore, their helper files or modules work and the extensions are able to launch external browsers normally. Then I'd uninstall them, get their crx from that extensions vault website and deploy them locally, install their helpers etc and they will fail just like 'Open with'.

Yeah.. fuck Google.

[OxGGGxOG3]

Thanks defaultx,
I also added the allowed_extensions described below and it works!

[OliverMD15]

Shame to hear, but an understandable decision. I use it on a daily basis with Vivaldi on Windows, so the constant disabling is quite annoying, hope someone finds a solution. Surprised it still works no issue in Opera, even though I got that through the chrome store too.

[tulextreme]

Hello! Your work have made me download a lot of useful tutorials from youtube in a snap! So handy and useful and i thank you for that! Edge now has blocked the extesion which made me very sad! Is there a work around for this? I dnt care how awful google might be just want to use this gr8 extension once again! (using Firefox as a work around but...) Thank you

[nicolaasjan]

Edge now has blocked the extension which made me very sad! Is there a work around for this?

Could you try the workaround I mentioned in this Reddit thread?

Just tried it myself in Edge in a virtual machine and the .crx file installed fine here (dragged the .crx into edge://extensions/ in developer mode)...

In case some extension is blocked, you can use the ADMX Templates for Microsoft Edge.
Tutorial here.

Then you can use the Group Policy Editor (gpedit.msc) to whitelist a specific extension ID (in this case cogjlncmljjnjpbgppagklanlcbchlno).
Screenshot.

(the Group Policy Editor isn't present on Windows home editions)
Then just use Firefox instead.

Note however, that in the near future Manifest v2 extensions will be deprecated in favour of Manifest v3, which means that this extension will stop working, if not updated.

[firejack007]

Chrome by Google violates New Tab Tools extension policy. 🙂

[mscha]

Can you perhaps update README.md to include this information, in place of the (now dead) link to the Chrome store?

[Igetin]

The website also still links to the Chrome Web Store.