Solved Support Extensions
-
This post is deleted! -
This post is deleted! -
why delete posts?
-
@callionifabio The posts were deleted as they were getting incredibly off topic. This topic is about supporting extensions on android.
-
Definitely need extensions. If I could install Dark Reader and uBlock then Vivaldi would be the only browser I need on mobile.
-
This post is deleted! -
For me it would be very helpful to have 'Vanilla-Chrome' available to manage cookies. I use it with the desktop Vivaldi.
Is there another option to manage, delete cookies on Vivaldi for Android? -
@Stardust said in Support Extensions:
Ublock Origin
I can only agree to that! A support of extensions for Vivaldi Android, especially for bloockers, would be very desirable and would make the browser much more attractive.
-
Instead of admitting extensions, it would be enough to be able to import the corresponding uBlock and nano filters, all available on github. That would not be necessary go through the Chrome Store.
I use Kiwi as a second browser, which supports Chrome extensions, but installing them there is quite messy on a mobile.>Laptop Lenovo V145 15AST, AMD A9- 9425 Radeon R5 - 5 cores 3,1 GHz RAM 8GB, GPU 2+1 GB SSD 256GB -Win10 64 v22H2| Vivaldi last stable|
-
@Catweazle said in Support Extensions:
Instead of admitting extensions, it would be enough to be able to import the corresponding uBlock and nano filters, all available on github. That would not be necessary go through the Chrome Store.
This topic is specifically about extensions, though.
Extensions also include things powerful like user script engines (Violent/Tamper/Grease monkey), not only blockers.I use Kiwi as a second browser, which supports Chrome extensions, but installing them there is quite messy on a mobile.
In Firefox for Android, for instance, it is not messy.
But the problem with Vivaldi for Android is probably indeed the fact that Chrome browser and store have no support for mobile.
-
@jesus2099 , Kiwi is also Chromium based.Well, perhaps this is why Chromium Android does not have support in the Chrome Store, there are only alternatives to have an own app store or to use github scripts
-
https://www.xda-developers.com/brave-browser-android-dev-would-add-extension-support-2020/
As Brave is open-source - if they do it, every Chromium browser can benefit, including Vivaldi.
So right now it might be wiser for Vivaldi to focus on other things to improve in the mobile browser. -
@LonM kiwi browser - Android Browser. have chrome web store.
if he could managed it, then i think vivaldi can do it too
-
@Deyirn said in Support Extensions:
@Hadden89 said in Support Extensions:
@lonm Chrome never supported extensions on mobile.
And always been quite heavy on cpu/ram on my phone, like Firefox (even without extensions).
But most useful extensions may actually work on android.Hmm, that's strange. Kiwi browser is a Chrome fork on Android, even in the Play Store and last time I checked, it allows you to install Chrome extensions as if you were on desktop.
Right now Kiwi is the only mobile browser for me that is worth using.
Yandex browser supports Chrome extensions too so it's not impossible to do it with Vivaldi too.
-
@Dr-Flay said in Support Extensions:
I would suggest adding support for userscripts.
It would be great if userscripts were implemented, if they work with PWAs as well. I've been using one recently on desktop and it would be fantastic to have it on mobile as well.
-
The main reason I use FF mobile is because there is a working userscript extension.
With that I have a wide selection of extension replacements I can use. -
Extensions are a must for me because of uBlock origin.
-
I would like to see support for extensions like Violenmonkey or uBlock.
-
Meanwhile Firefox Preview (Nightly) gets the first supported add-on: uBlock Origin.
https://www.neowin.net/news/firefox-preview-nightly-gets-support-for-one-add-on-more-should-arrive-soon -
@Stardust said in Support Extensions:
Meanwhile Firefox Preview (Nightly) gets the first supported add-on: uBlock Origin.
https://www.neowin.net/news/firefox-preview-nightly-gets-support-for-one-add-on-more-should-arrive-soonThis really illustrates some important things to keep in mind while waiting for Vivaldi to implement these changes.
With the resources Firefox has at its disposal, they are way behind where they thought they would be with this project. Back in June they were saying they would have a feature-rich polished version of Firefox Preview in the Fall. Yet extension support is just now, in February, only hitting nightly builds, not even Firefox Preview's more stable release.
This shows just how difficult extension support is to get right. Vivaldi Beta is impressive in its stability, and that comes from attention to QA and not releasing features that are half baked. I wish I could have what I want when I want it (which is always now of course). Having built a career in Quality Assurance, I appreciate a project that demonstrates a dedication QA and can temper my expectations on time when I receive quality in the end.
Additionally, it's a bit of stretch to call what the nightly build is getting support for extensions (plural). There is only one extension that will be available, uBlock Origin. This lends further weight to the previous point about how difficult it is to support extensions, but also leads into the next important point to keep in mind.
Firefox has outsourced ad-blocking. That's what is actually being released, not support for extensions. They are including ad & tracker blocking, but they aren't doing it themselves. As has been discussed in countless places, no browser has native ad-blocking that is as complete and configurable as that which dedicated extensions provide. Firefox has implicitly stated that as well, by making uBlock Origin the ad-block provider for Firefox Preview on Android.
People who take their privacy & security seriously don't rely upon native ad-blocking features in any browser where extensions are available. Vivaldi has made public statements to the same effect, about giving users access to the best ad & tracker blocking functionality through their support of extensions, rather than implementing a complete blocking feature set internally.
So this should help to set our expectations. The best way for us to get ad-blocking is via extension support. Vivaldi doesn't have the same level of resources as Firefox, and their first release of Firefox Preview was back in June. Here it is Februrary, and one extension is only now hitting the nightly builds. I'm not sure how much longer it will be before uBlock Origin is available in Firefox Preview (regular), but whenever it happens that should give us a lower bound on the minimum amount of time it would likely take to get extensions implemented at a level of quality that is acceptable to release. Or perhaps better to wait until FFP supports more than 1 extension in the regular release as a marker.
In the meantime, continuing to use Vivaldi, reporting issues we find and discussing ideas on how to improve the browser will help move the project forward at a faster rate. Especially the part about submitting detailed bug reports including all the info detailed on Vivaldi's bug reporting pages. The additional testing is something is very difficult for small teams to make up for through other means such as creative problem solving and process optimization. It's simply a resource intensive aspect of software development, nothing can replace the wide variety of devices and configurations of real world use. Think of every well written, reproducible bug report that you submit as a donation to the project, in some ways it's better than what you would have given financially.
Edit: accidentally submitted too soon, finished off the post with the last paragraph (and maybe another line or two as well).
