-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No installation button on chrome webstore #31
Comments
The button div is added by |
The url I'm visiting is this: |
Errors are shown on the extension "cards" only if they actually occur. I'm not really sure how to debug this further as everything seems in order; my best guess is still that somehow chromium is blocking the extension from modifying the HTML of Chrome Web Store pages. I added a context menu option (3542d44) similar to the other extension you were using, can you try this updated version and let me know if this workaround at least works for you. |
The workaround works fine; I can see the context menu. I just set the extension to work in incognito, and when I open up an extension page in an incognito tab, the button is there. There must be some other extension interfering with. I'll get back to you when I figure out which one. |
It seems that there are multiple extensions that interfere with it.
Out of all my extensions, those where the only 2. I'm getting rid of ComposAI because it seems like it's probably tracking me, but compatibility with ghostery would be nice. Or at least mention on the page that if people are using ghostery, they should make sure to press "Pause Ghostery" and then later re-enable it. |
Nice find, it appears Ghostery adds its own <div> which interferes with chromium-web-store's content script. It should be an easy fix to make chromium-web-store compatible with Ghostery. |
Well, I'm not sure why is this implemented this way and what was the idea behind it, but it doesn't seem genius to me. I'm trying to download extension from a different browser a browser that has access to internet, then download the extension and install it in a browser that is in Interanet (doesn't have access to internet). The problem is when I download via chrome, it immediately installs it on the browser that has access to internet, which is not what I want to do. I want to be able to download it as a FILE which with this implementation it become impossible. There is a saying in my culture, which says "Scientists become great scientists and then become mad scientists" A much easier solution would be to just have a download button and then register file extension to open with browser which would make both installing from local and online similar and for non-windows systems, just intercept the download. Developer go to so much effort to make this feature so complicated that become completely useless. |
Hey not sure if this issue is still being worked on, just came to say the workaround of using incognito worked for me! I'm installing |
Just want to mention: there is a context menu option you can use if the button isn't enabled correctly. Simply right click > Add to Chromium |
Expected behaviour:
When going to the chrome webstore on any extension, there is a "Add to Chromium" button that allows the user to install the extension.
Current Behaviour:
When going to the chrome webstore and attempting to download any extension, there is no "Add to Chromium" button as shown in the video here.
Steps to reproduce:
Possible Causes:
I previously had an extension installed that allowed me to install extensions via a context menu when on the page. Here is the other extension.
Using this tool, I installed various extensions but just recently switched to this one for version management. There could be some interference between these two, although when I added the chromium-web-store extension, it properly showed the new updates and also installed them when I clicked "Update all extensions".
I also made sure to disable that other extension and went as far as uninstalling it. Neither worked.
Environment
I'm currently running ungoogled chromium version
84.0.4147.89 (Official Build) Arch Linux (64-bit)
, which I compiled from the latest ungoogled chromium version on the AUR.Images
Expected behaviour:
Current behaviour:
The text was updated successfully, but these errors were encountered: