You also can't import bookmarks on Android. The officially recommended way is to sign up for a sync account and verify it (they don't accept throwaway emails), install on desktop, import on desktop, then sync to mobile.
replyProbably it's a very low request priority. I use Vivaldi on Android with the built in blocking at strict. The last thing I remotely have interest in are Extensions in Android Vivalid.
replyBecause of stuff like this?
https://news.ycombinator.com/item?id=48207660
replyIf you don't have the ability to police extensions you're basically putting your users up for sale?
But they support extensions on desktop.
replyThe problem you linked to also happened on desktop because there is no VSCode for phones.
Your users don't have to use those extensions, so I don't understand how that's relevant? People who do, should be made aware of risks and that's it. This is not a good argument against taking away their option to have that customization.
replyI'm having a hard time finding a thread where people don't complain about npm when the real issue is packages being compromised.
replySwap packages for extensions in the above and let me know how that's different
But what's your argument? That phone-based extensions are more vulnerable somehow than desktop extensions?
replyIf anything, wouldn't a phone extension be more sandboxed than most desktop environments?
How is this an argument when you can use extensions on the desktop version?
replyNo, if that were true, there would be no extension support on non-mobile
replyThey can add support for Chrome and Edge extensions marketplaces.
replyI use on desktop Vivaldi, on Android I can recommend Cromite (some people like as well Helium and Ultimatum)
reply