New windows cannot be opened in alternate desktops/spaces
adrianlafond last edited by
On Mac, you can have multiple desktops (formerly called spaces, created through Mission Control). But in Vivaldi, you cannot switch to a different desktop/space and then open a new Vivaldi window. New Vivaldi windows can be opened only in desktops/spaces in which there is already an existing Vivaldi window.
This is not an esoteric problem: Vivaldi is the only app I have ever encountered which fails this. I depend on multiple spaces to work with multiple projects simultaneously, so this basically makes Vivaldi useless to me because it's such a pain to open new windows (I use Opera instead as my default browser). I've filed bug reports on this, the first quite a long time ago, probably a year or more, but this never gets fixed.
@adrianlafond I've been frustrated by some of the same issues as you. Vivaldi's window management on macOS is definitely a bit broken in some cases, even with the "Use Native Windows" option enabled.
Would it be possible for you to share the ID's for the bugs that you've filed? Given that the problem most likely lies in code that Vivaldi did not write themselves, it may be a while before we see a fix. However, as users, we can still point out the issues that impact us day-to-day... and hopefully can influence the priorities of bugs that have already been filed.
adrianlafond last edited by
@xyzzy I could not find the bug report form that I have used previously so I doubt I can pull up the exact IDs. In any event, the issue has been logged here at least.
No, I definitely don't understand everything about Vivaldi, but why would the issue not involve code that Vivaldi wrote? It seems to be only a Vivaldi issue that effects no other Blink-based browser (Chrome, Opera, Brave).
@adrianlafond I don't work for Vivaldi but I'll do my best to explain things in a bit more detail.
Vivaldi actually incorporates components from many open-source projects. From the macOS menu bar, go to
Vivaldi / About Vivaldi, then click on open source software to see the list of credits.
Vivaldi is also different (from say, Safari) in that it's not a typical native Mac app. The developers adopted a platform-neutral approach which significantly reduced development time and allowed them to implement features (simultaneously on Mac, Windows and Linux) very quickly. Vivaldi is basically Chromium at its core but the UI is implemented in another layer of code using web technologies and rendered like a web page. Even the windows themselves are an emulation. (If you inspect the colours of the "traffic light" window controls with the Mac's "Digital Color Meter" utility, you'll see that they're different from those on a true native app like Finder.) However, if the emulation has bugs or the macOS integration code is incomplete, you'll run into issues here and there like the one you reported in this thread.
FYI, Firefox also does not always work quite right with Desktops/Spaces. It's not a true native Mac app either - its UI is implemented in XUL, which also draws its own windows and emulates the native widgets on multiple platforms.
Back to Vivaldi... I believe the issue is fixable, but I don't know whether the problem actually lies in a 3rd-party component used to build the browser (with Vivaldi waiting for a bug fix) or if the Vivaldi developers need to enhance their own code to integrate better with macOS, or both.
The good news is that many of the Vivaldi developers are Mac users themselves. Hopefully we'll see a fix for this bug from one of them eventually... and hopefully sooner rather than later. :-)
If I find out any more information, I'll post a follow-up.
Cellane last edited by
@adrianlafond Do you mean you're unable to have multiple Vivaldi windows open at the same time with each occupying separate desktop/full screen window? Because I don't have issue with that, or rather – I have slight issue with it but I can make it reliably work, anyway.
What happens for me when I press Cmd-N with Vivaldi occupying its own desktop is that sometimes (I'd estimate roughly 60% of the times) the window doesn't get moved to its own desktop as anyone would expect but rather opens on top of the existing Vivaldi window, which is just weird as hell. At any rate, if I click the green Maximize button on that newly opened Vivaldi window, everything gets corrected and the window moves to its own space. For the record, I do not use the native windows.
Speaking of issues that I've only ever seen in Vivaldi and not in any other Mac app, I've never seen an app that takes so long to open another window (sometimes I'm waiting easily 5-8 seconds for new anonymous window) and I've definitely not seen an app that manages to mess up its own tab bar quite frequently, placing new tabs behind existing tabs (making them only accessible with Ctrl-(Shift)-Tab) or leaving huge empty spaces in between two tabs.
@Cellane The issue for me is that it's not quite as easy to open a new initial Vivaldi window in another Desktop. If I have Vivaldi open in
Desktop 1and nothing in
Desktop 2, getting an initial Vivaldi window into
Desktop 2requires first opening a new window in
Desktop 1then moving it to the new Desktop.
With Safari, Chrome and even Firefox, I can simply switch to a new Desktop, right-click on the Dock icon and open a new window from the context menu. With Vivaldi, this only works if there's already another Vivaldi window present in that Desktop.
Cellane last edited by
@xyzzy I see what you mean now! I'm sorry, I made the incorrect assumption that you mean opening new Vivaldi window as a full-screen Vivaldi space/desktop. Yeah, what you are describing definitely doesn't work the way anyone would expect.
@Cellane Thanks for confirming this glitch as well. I'll file a new bug and hopefully it won't be too hard for the devs to get this fixed.
FYI, getting browsers like Chrome/Chromium and Vivaldi working right on macOS is tricky because their inherent design doesn't always mesh cleanly with the Mac's application model. Here's an old blog post by one of the Chromium team's Mac developers that describes some of the hoops they had to jump through to get things working seamlessly. Getting the Dock integration right was especially painful. The content is a bit dated (and some things have changed from a technical standpoint) but it's still a fun read.