Extension Installation from Opera Catalog
-
There are well-tested extension, which cannot be found in the Chrome catalog.
-
Workaround
(But I'd prefer a Vivaldi Catalog for such missing extensions) -
I preferred to install my extensions directly from Github, instead of the Opera Store. I trust the current Opera less than Chrome
-
@Catweazle Yeah, I also prefer to do that: If I have to use an "unsupported addon" I go with unpacked or a crx.
-
I'm also curious, what better extensions does Opera have then? Because what I've heard from extension developers is that Opera Store is the hardest to work with (delayed publishes and updates).
-
@madiso Opera catalog have addons with support for sidebar (which can almost be used as webpanels) and some extensions not allowed due in chrome store due their terms of services. But, yeah, usually are less updated (which is not always bad, if the extension is non security related).
-
@Hadden89 said in Extension Installation from Opera Catalog:
@madiso Opera catalog have addons with support for sidebar (which can almost be used as webpanels)
Hmm, current Vivaldi lets you use any extension's popup as a web panel.
- Open the popup of an extension
- Right click > View Source
- Copy the URL without view-source:
- Use it as a web panel
Not as convenient as an official method would be, but it's possible
But, yeah, usually are less updated (which is not always bad, if the extension is non security related).
It is bad. Developers cannot fix issues and users cannot get the fixes. If anything, Vivaldi could add a feature to check for extension updates manually but I wouldn't recommend it, all Chromium-based browsers already warn when permissions change.
some extensions not allowed due in chrome store due their terms of services.
That's a good argument, although due to the updates again I think an external source like the suggested GitHub would be better.
-
@madiso said in Extension Installation from Opera Catalog:
current Vivaldi lets you use any extension's popup as a web panel
That's true. But extensions from Opera Store have a
sidebar.html
which is already adapted to dynamic webpanels|sidebar resize.
Still have to be loaded with the URL method you explain.It is bad. Developers cannot fix issues and users cannot get the fixes.
I had few extensions broken in Vivaldi due a [forced] update whereas the Opera version worked being "legacy".
This as a lot of extensions are tested only on Chrome. Often on Opera and Edge, but only cause they have a store.
Then I ended to unload them as unpacked modifing the Update URL to localhost (which is something "nomal users" shouldn't do ever).The better route would be:
- Vivaldi Store (*.VRX?) + packages history (independent from chrome TOS)
- CRX from Google Play (with the slight risk to have "borked" updates) and other sources* (in such case I'll go with point 3)
- Unpacked (best on sites like github)
- Other store supports (which is not useful with point 1)
-
I had some extensions broken in Vivaldi due a [forced] update whereas the Opera version worked being "legacy".
This as a lot of extensions are tested only on Chrome. Often on Opera and Edge, but only cause they have a store.
Then I ended to unload them as unpacked modifing the Update URL to localhost (which is something "nomal users" shouldn't do ever).I use a lot of extensions and I haven't had this kind of issue, perhaps you are actually experiencing a bug with Vivaldi itself? E.g. Vivaldi does not currently support address bar search engines that are added by extensions.
The better route would be:
- Vivaldi Store (*.VRX?) + packages history (independent from chrome TOS)
I agree, and it has been suggested previously. I think this is the one:
https://forum.vivaldi.net/topic/36632/support-webextensions-and-improve-them-too -
@madiso Webextensions support in Vivaldi need an update.
But I'll start to stay closer to the standard adding what it misses [from chromium] and the WebPanel API.
[I'm not expert, but "forking" as Firefox and Opera did with unique APIs/calls is a big task. And our team is small] -
@madiso
Two years ago, when I opened this topic, it was a different situation. Since then, the company has made it a pain in the back to publish extensions in their own catalog, because of the VERY long moderation process. I don't know how many developers have left the catalog since then, or how many extensions are still under active care. -
@Hadden89
The only drawback is the lack of auto update. I know, many extensions just work well, but it is far from ideal. -
@madiso Few addons affected by the "cut popup master bug" (forgot the VB).
For non critical extensions - as the extension managers - using a "legacy (unaffected) version" is ok, for others - as cookie managers - I just searched for a replacement.
Now I've increased the UI size to 87% which seems to resolve some of these quirks. [included some uncentered favicons] -