Vivaldi does not support native macOS features

  • Some features in Vivaldi could be from OS itself and not from the browser, things like

    • "Look Up" does not work from Vivaldi, if you select a text > right click > look up it will not work
      -- Same for 3 tap in a TouchPad

    • Ctrl+Command+Space: Should bring emoji browser, but vivaldi is not supporting text tools from macOS

    • Spell checking is does not use the system embed one, this is really bad for multi-language users, macOS support multiple languages natively and as a Brazilian working in Ireland, I don't want to set my browser to a single language, just to use spell checking

    • Edit menu in general don't have any AppKit default features from macOS

  • I can see some topics are related to this issue

  • One of the reasons I am considering scrapping Vivaldi and (God help me) going back to Safari is text expansion that Vivaldi simply doesn't do. This is a HUGE downside, in my opinion. I have many piece of information that I have to type repeatedly. I have set each one up under my Mac System Preferences as a keyboard shortcut. For example, when I type the letters "addy" my Mac will automatically expand it to my full mailing address. I have set up probably 30 of these and they are massive time savers. They all work within my email program, in Preview when I'm editing PDFs and it works in Pages, Numbers and yes even in SAFARI. Yet Vivaldi won't do it. I have searched in Vivaldi's preferences, I have Googled it to see if I'm missing it, and I can find nothing about it. This seems to be impossible. I hope I am wrong, because it would make a WORLD of difference in the function of this browser. Thanks!

  • Moderator

    (Big sigh...) You're all right when it comes to frustration with UI issues, missing basic features like a Bookmarks menu, and lack of integration (with Keychain, Services, etc.) that we love and take for granted in native macOS applications. However, it's also important for us Mac users to continue to use Vivaldi as much as possible; the more of us that there are, the more that they'll invest in making the Mac experience better. (As a company, they're also striving for success "despite" having good corporate values, so I feel the need to support that too.)

    I don't work for Vivaldi, nor do I have any insight into their plans or timelines. However, they've made no secret that much of their internal focus is on upcoming "mega" features like Mail and Sync. Once these features start to launch, and if we do our part by continuing to provide constructive feedback and keeping Mac "usership" up, hopefully Vivaldi will reinvest freed-up developer time into improving macOS integration and closing the gap with native apps. Until then, I still think that Vivaldi is an awesome browser and MUCH more usable than Chrome or Firefox.

  • I just don't get why it don't use basic AppKit features, if it was build in over AppKit most of this would come for free, including services, text support, etc... It just need to be build natively.

    I am trying to make Vivaldi my main browser there is a lot of features that I enjoy, but the lack of integration is frustrating.

  • Moderator

    @rosorrentino: Vivaldi is trying to build a SINGLE browser with the broadest possible application, making tweaks and patches as necessary for different operating systems. This is largely possible, because it is built using web technologies and most systems see the web the same. To build on appkit, they would have to build an entire separate browser just for Mac, and that's not practicable - especially since it would take the same amount of personnel and resources as the Windows version takes, for a tiny fraction of the users that windows has, and they don't have twice the crew to do it. Chromuim already exists, not built on appkit, and it's basically compatible with all modern systems. So Vivaldi is built on that.

  • Moderator

    @rosorrentino Further to @Ayespy 's comment, one of Vivaldi's earliest design decisions was to develop code using cross-platform toolkits (and to avoid using native widgets) as much as possible. This was (apparently) based on some hard lessons learned back at Opera where they were often struggling to implement new concepts and UI innovations consistently across all platforms, while also having to cope with limitations unique and specific to each platform's toolkit(s). (Imagine what it would be like to implement a Tab Stacking widget (that can also be dragged and dropped) and having to write/rewrite/re-rewrite platform-specific C/C++/Objective C... code for Linux, macOS, and Windows, and eventually mobile platforms as well.)

    Unfortunately, with Vivaldi's approach, cross-platform toolkits do a less-than-ideal job mimicking native widgets, it can be a challenge getting snappy performance when rendering the UI and browser chrome with web technologies, and platform integration is what it is. (Take my opinions with a grain of salt. I'm definitely in the "I prefer native widgets" camp, and strong native platform integration and adhering to platform conventions matters a lot to me. I also preferred Camino to Firefox even though it had only a fraction of the features.)

    Fortunately, with Vivaldi's approach, we also have a feature-rich browser supported equally on macOS, Windows, and Linux that was developed in a very short time; an amazing feat.

    We Mac users still have every reason to be optimistic -- many of Vivaldi's developers are Mac users too who have a vested interest in making the Vivaldi experience on macOS as good as it can be.

  • @Ayespy

    Yeah, suggestions of switching to AppKit are probably nonstarters. Stuff like "Look Up" and Ctrl-Command-Space to bring up the Characters browser seem likely to be doable though; Chrome has those working.

    As for spell-checking, I'm noticing that in both Vivaldi and Chrome on OSX, no matter which languages I have added in Language Settings (chrome://settings/languages or right-click on text, select "Language Settings"), even if I just have English set (you can multiple languages set), the red zigzag underline appears only under words that don't match any word in some multi-language (but not every-language) wordlist. (Some testing results of mine: Correct English, Portuguese, Russian, and Spanish words are not red-underlined. Hebrew letters it doesn't even try to spellcheck. For Aafrikans text, Vivaldi red-underlines a lot of words but not all, presumably recognizing some from a Dutch wordlist.)

    Also, in both Vivaldi and Chrome on OSX, although there is a context menu option to add a word to the dictionary, there is no way to edit or remove such words once added. In Windows, chrome://settings/editDictionary lets you edit it, and in chrome://settings/languages/ there is an option at the bottom to enable/disable spell checking entirely as shown in screenshots at - something missing from chrome://settings/languages/ on OSX. (Submitted as a bug, just now.)

  • Thanks for all clarifications and great feedback.

    I am really trying to continue to use Vivaldi, for many reasons that I like, but the dictionary, emoji and Look Up are things that I use a lot.. Hope to get it soon

  • To the top! We need this.

  • It's even doesn't support url opening properly. I opened url to reset password for this forum (from email). And got errors until copy and paste url manually…

    Btw, password reset page seems broken.

Log in to reply

Looks like your connection to Vivaldi Forum was lost, please wait while we try to reconnect.