There is a reason that prevents me to move to new browsers from Opera 12 (many tabs in one window)



  • @Username_:

    @guzul:

    I just hope they implement tab bar scrolling. You set minimum tab's width, lets say 20 pixels (favicon+borders) before scrollbar appears. It lets you choose how much you can see from tabs (favicon, x close button or even title with width over 150px) and you still are able to display from 40 to 50 tabs. Firefox is doing it for so many years and it just frigging works (just the option how wide the tab is, is hidden in about:config). I don't understand why any other browser does not support it. It would even work better on tablets with fat fingers, you can swipe to scroll through tabs, and easily select correct tab without any "ninja" skill to select tab that is 2 pixels wide.

    bar scrolling is bad idea. that's why i'm still using opera presto 🙂 but not firefox 🤢 .
    10 pixels tab can be useful as well as 20 pixels

    Do developers read this forum usually or at least sometimes? :whistle:

    I'm sure they do. If you read my previous post carefully you would understand that you would have a possibility to set it to whatever size you want?

    I proposed this before, but I'm sure nobody have read that.
    You would have an option for it, if you set minimum tab width to 0, you would have current behavior, if you set it to something bigger than zero, scroll bar would appear when tabs get to this size.
    Simple and logical. Default would be 0 of course, for clumpy tabs lovers 😛 .
    This would solve tabs overlapping when tabs would be set on side, which looks really bad right now.

    [attachment=756]scroll_please_2015-03-02.jpg[/attachment]
    Attachments:


  • Moderator

    This is how it looks in the latest Vivaldi build with Tab Tooltips (i.e. Previews) disabled:



  • @Pesala:

    This is how it looks in the latest Vivaldi build with Tab Tooltips (i.e. Previews) disabled:

    Good, good 🙂
    Anyway, I reaaaaaly hope for scrolling (optional, because most don't want it?), to solve my problem from above.
    I will just wait and see, if this is not solved in future I'm sorry but I don't see it much as a professional browser. Just like Chrome which is more like tool. I managed it with Outliner, but it's not so comfy because it's in a separate window. So I'm working in Firefox now, but man it's slow and it's worse and worse since version 29.
    I work in visual design and game dev, and I need around 150-200 tabs open with scripting docs/git, and I don't have time to look at hints… I have to point to a correct tab, switch to it, copy some code and move on. For me scrolling is faster, usually having a bit more than one screen space of tabs takes just a half of a second to scroll, pick up a tab with eyes move mouse a little and click.

    Anyway keep up the good work, time will tell if I will switch to Vivaldi or not. Cheers



  • @guzul:

    I work in visual design and game dev, and I need around 150-200 tabs open

    That'll be a while before Vivaldi can do that, I reckon. Right now, it starts slowing down a lot when you get over something like 20-30 tabs and with 50 tabs, it's terribly sluggish. As is pretty much every other Chromium-based browser, including the current Opera (which is actually best of the bunch right now in this regard).



  • @Case:

    @guzul:

    I work in visual design and game dev, and I need around 150-200 tabs open

    That'll be a while before Vivaldi can do that, I reckon. Right now, it starts slowing down a lot when you get over something like 20-30 tabs and with 50 tabs, it's terribly sluggish. As is pretty much every other Chromium-based browser, including the current Opera (which is actually best of the bunch right now in this regard).

    Indeed it's slow with this many tabs on more demanding webpages, and "The Great Tab Suspender" extension which I use in Chrome does not work in Vivaldi. But nonetheless I tried it at work, only disturbing thing was that tabs overlapped badly (this is why my rant). With 40 tabs selecting tabs was really inaccurate, sometimes wrong tab is selected. Unfortunately I can't use it as it is now. Hope devs will look into it and will not just close an eye and avoid the problem. :huh:



  • Well, no any answer from dev. 😞



  • @guzul:

    Indeed it's slow with this many tabs on more demanding webpages, and "The Great Tab Suspender" extension which I use in Chrome does not work in Vivaldi.

    Give the needed time to the Vivaldi developers.

    In the meantime…

    https://vivaldi.net/en-US/forum/all/2754-lazy-tabs-workaround



  • @Pesala:

    This is how it looks in the latest Vivaldi build with Tab Tooltips (i.e. Previews) disabled:

    Ahhh… (:relief:)
    Thanks, Pesala !!

    I had looked for that setting at least a half-dozen times, but somehow hadn't noticed "Use Tab Tooltips" rather than "Use Tab Previews".

    The tab previews are great on a system with enough horsepower, but can cause severe lags on an older low-end system.


  • Moderator

    IMO the wording in settings is wrong. It should be "Use Tab Previews."

    When it is disabled, then Tab Tooltips are used by default. I still prefer the large tab tooltips in Opera 12.17, and there tab-stacks use the previews anyway.

    In Vivalid, with Tab Previews disabled, and Tooltips used instead, the Tooltip for a tab-stack only shows the active tab's title, whereas in Opera 12.17 one can see previews of all tabs in a stack when tab previews are disabled.



  • @Pesala:

    IMO the wording in settings is wrong. It should be "Use Tab Previews."

    When it is disabled, then Tab Tooltips are used by default.

    You're right! It's backwards, isn't it. I was so relieved to find it, I didn't notice that.


  • Moderator

    They read it all the time, but don't have an answer to every question, just yet.



  • Pesala

    tooltip = tab preview

    so it's written well 🙂 the problem is that we used to know it as "tab preview" and the "tooltip" terminology is just not too well-known for us. (which means the same as tab preview).


  • Moderator

    @ahoj1234:

    Pesala

    tooltip = tab preview

    so it's written well 🙂 the problem is that we used to know it as "tab preview" and the "tooltip" terminology is just not too well-known for us. (which means the same as tab preview).

    It's totally non-intuitive unless you're immersed in coder-think. The term "tooltip" was coined to refer to the tiny text label that pops up to give the user a tip as to what tool icon or word he was hovering at that time, is meant to do. Hence, "tooltip." However, the same coding function can be assigned to what (of any sort) pops up when when you hover ANYTHING. That is to say, the coder treats tab previews, for coding purposes, the same way he might treat any "tooltip." Hence, the non-intuitive label in the Settings page. IN FACT, if you disable "tooltips," you no longer get previews but, instead, get an actual text tooltip. SO, I recommend the developers change the word in that option from tooltips to previews - so that we ignorant non-coding users can understand what you're talking about.



  • @ahoj1234:

    so it's written well 🙂 the problem is that we used to know it as "tab preview" and the "tooltip" terminology is just not too well-known for us. (which means the same as tab preview).

    I'm not a coder (so correct me if I'm wrong), but it seems to me the problem is that we used to know "tooltips" as, …well, ..."tooltips", and historically they don't mean the same thing at all.

    For example, a "tooltip" for an image on a web page is typically informational text about the image HTML coded using the [<title>attribute</a> (syntax <element title="text">) or sometimes the <a href="http://www.w3schools.com/tags/att_img_alt.asp" target="blank"><alt> attribute</a> (syntax <img alt="text">) that appears when the mouse is hovered over the image.<br /><br />Per the venerable <a href="https://en.wikipedia.org/wiki/Tooltip" target="blank">Wikipedia</a> (and my own personal recollections), the term <em>"tooltip"</em> originated with early Microsoft products (e.g., Win95) as informational text to clarify the title/meaning/purpose of various icons on the Task Bar; but of course they are now used in the same way for numerous other elements of a UI.<br /><br />It seems to me a text description of the tab element (i.e., the <title> Page Title</title> as encoded in the page HTML) is precisely what we see in Vivaldi when the option to Use Tab Tooltips is de-selected (instead of when it is selected), and why I said "it's backwards" above. To make logical sense, either the wording in the settings needs to be changed to Use Tab Preview (which I imagine is the developers' intent), or the text tooltips need to be used when the box next to the current wording (Use Tab Tooltips) is checked (opposite of how it is now).

    @Ayespy:

    …That is to say, the coder treats tab previews, for coding purposes, the same way he might treat any "tooltip." Hence, the non-intuitive label in the Settings page. IN FACT, if you disable "tooltips," you no longer get previews but, instead, get an actual text tooltip. SO, I recommend the developers change the word in that option from tooltips to previews - so that we ignorant non-coding users can understand what you're talking about.

    I would (more or less) agree with this in the sense that Tab Previews are probably HTML coded in some way similar to tooltips (I don't know how exactly) and they function like tooltips (appear upon mouseover and provide more information). But previews are different in that they are not text, but an image (thumbnail) of the web page on the tab. They do, in fact, provide information to the user about what is on the tab's webpage, but in the form of an actual visual image preview of the page contents, not an abstracted, summarized text description of the page contents (tooltip).

    So they are two different ways (Vivaldi options) to achieve approximately the same thing. The problem is that to be a user-selectable option they have to be labeled differently somehow, and the Vivaldi settings would make more sense if (image) previews were not mis-labeled as (text) tooltips.

    Of course, they are also functionally different (my main concern, and why I'm glad there is an option) in that tab image previews of a page consume considerably more resources than a simple text description (text tooltip).](http://www.w3schools.com/tags/att_global_title.asp)



  • PREVENTS ME TO MOVE TO NEW BROWSERS FROM OPERA 12:
    1. internal mail + rss. The webmail is not a well substitute for full-featured mail client
    2. linked from mail contacts
    3. notes (!!)
    4. Bookmarks not so very important, but yet

    I use like IT-director Opera in corporative workspace. This function is very important and using for workers intensive (if there is somebody, who can point to that and teach).
    For example, the one file (3 text strings) on the proxy-server and .ini file for Opera 12 point to the proxy server on client-side better, then do this throw group policy for all client system (i.e. Chromium use system proxy settings, it is bad).
    Try to speed-up and measuring connection to collaborative portal http://go.vpa-expert.ru. For our measuring Opera 12 parse and show login page three times faster GooChrome and Firefox. Is this significant ?
    One more reason: Chromium-based browsers opens different number of processes with big memory exploration. Reasonable limit on the number of program instances and memory consumption can not be done with built-in abilities.



  • @umnik:

    PREVENTS ME TO MOVE TO NEW BROWSERS FROM OPERA 12:

    3. notes (!!)

    You could perhaps be more specific as to what exactly are you missing in Vivaldi notes.


 

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