Move Tabs into Title bar of System Window

  • it would be pretty awesome to have the ability to have the tabs in a system Window, similar to what chrome does. it gives the benefit of not looking totally weird in the rest of the system, while saving space at the same time.

  • Moderator

    @my1 What is your OS? That is the default on Windows if I recall correctly.

    Settings, Appearance, and uncheck "Use Native Window." Then restart.

  • the point is that the tabs should be in a title bar OF A NATIVE WINDOW (basically called "system window" in the german settings).

    vivaldi without native window looks plain weird in contrast to all the other windows.

    1_1531310742029_Screenshot (469).png

    chrome and vivaldi on non-native vivaldi above, compared to vivaldi native below.

    0_1531310742028_Screenshot (468).png

  • It's not possible to have them in a native window, because as far as I know a native window is controlled entirely by the os or desktop environment.

    Instead Chrome builds its own ui that tries to emulate add best at possible the native UI.

    This fr might be useful:

  • Moderator

    @lonm Opera 12.18 achieves by overlaying the Tabs on the Windows Title Bar, without actually removing it, AFAIK.

  • Moderator

    I am puzzled. What is it that looks "totally weird" if one does not run Vivaldi in a native window?

  • The transparency, the lack of visible dividers between the window buttons ... looks like Windows 7. V doesn't integrate with Aero.

  • @Pesala well it doesnt fit, design-wise to the rest of the windows.

    @sgunhouse precisely

    @LonM well considering chrome/chromium even works nicely on completely custom themes there is totally a way it does work with a perfect native-style window without hard-building your own UI by choosing the theme based on the User's OS but instead use the theme resources directly, aka use a native-style window.

  • Moderator

    @my1 Browsers that are developed with native elements (pretty much every browser but Vivaldi) are much slower and harder to develop, and cannot accommodate the flexibility which is Vivaldi's main reason for being.

    Developing Vivaldi in a non-native window using HTML, Javascript, and related tools make it possible for a very small team to create an experience no one else can offer. For the sake of efficiency, it also means that Vivaldi looks the same on all systems (except for the three Mac stoplight dots) - which is fine by me, because it looks completely native on Win10 and, since I'm used to the Win10 look, I'm at ease with it on Win7 (especially since I have transparency turned off there to save on resources) and Linux Mint.

    But to make separate "native-looking" versions for different systems would overload the small Team and throw away the advantages gained by using non-native elements. Perhaps when Vivaldi has grown to a few hundred developers, this might be less of a consideration. For now, the Team can't do "like the big boys" and build from native (and therefore native-looking) elements for the reasons stated. It would take forever to develop, and features would be strictly limited.

    The ability of users to heavily customize the look of the browser somewhat makes up for this "shortcoming."

  • okay, I would have thought that especially with chrome as a base that vivaldi could take the native-window part stright from there.

  • Moderator


    My1 4 minutes ago
    okay, I would have thought that especially with chrome as a base that vivaldi could take the native-window part stright from there.

    Unfortunately, no. That would tie Vivaldi's hands as to customization. That's what all other Chromium-based browsers do, but then we would just be another Chrome clone. The developers would be unable to fulfill Vivaldi's promise.

  • @ayespy
    It is only a matter of resources to implement a native(ish) theme for supported systems. Imitating corner rounding, gradients and transparency of the given system inside the window is a relatively easy task. (Maybe the should only extend the possibilities of custom themes, let the users create the themes, and only choose the best and add it to the available selection.)

    However, styling the program window itself is another question. But it is an important question, because people like consistency. Well, some hardcore Presto/Vivaldi users might not be interested in this issue, but surely, the target group of the development is not only a small fraction of possible users.

    I don't know much about Linux distros or OS X, but Window 7 (with Aero) still has the strong second place on the market, and despite all the efforts of MS to force users to Windows 10, I won't be surprised, if they extend the support period again. More than that, transparency/translucency is coming back to Windows 10 with the fluid design, and Vivaldi should address this issue sooner or later.

    I don't say it's top priority (although it bothers me A LOT), and I understand the concept of the custom GUI, but this is a huge shortage of Vivaldi.

  • @nekomajin but the idea of having vivaldi apply themes by itself would also be very intresting. especially if users could create their own themes in regards to borders, buttons etc, making the window look however they want.

  • @my1
    That would be the idea of my feature request.

  • Moderator

    @nekomajin Complete custom theming is on the way, but still a good distance off. Sharing of user-developed themes or skins will be a part of that.

    I suppose some consider a non-native window a "huge shortcoming" of Vivaldi, but I find it irrelevant. That's just me. In fact I went exactly the opposite direction today, disabling aero and all animations and effects in my Win7 tower, to accommodate some experiments I'm doing that are really hammering its very, very limited resources (single-core processor 3GHz P4 and 2GB RAM). So I'm rockin' a nice Win 95 look on the box right now...

    We already have transparent tabs, so transparency I'm sure is not out of the question, to say nothing of rounding window corners...


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