Brave Browser introduces vertical tabs
brave.com
brave.com
Multiple panes with tabs, that can be resized either to custom sizes or automatically (binary space partitioning).
It’s too much for a general purpose browser, which is how we’ve got the Chrome, Safari, Firefox we have. But I think the appeal of a more information-dense browser is broader than we think, anyone doing research would benefit from it.
What are your impressions of it?
I use an ultrawide 32" screen and even for window tilling I use PaperWM (technically a Hammerspoon script because PaperWM isn't on MacOS). So I only need to navigate windows/tabs in one dimension (horizontally).
Arc does have the benefits of native UI, Vivaldi at least when I tried a couple of months ago was very janky, presumably because the browser chrome is written in React.
Somewhere in this thread people mentioned Stack browser which is actually closer to PaperWM in terms of how it tiles tabs. For both Arc and Vivaldi it's very annoying if you resize (going fullscreen and back) windows with tiles because the size of the tiles gets messed up. Stack just keeps the size and make them scrollable.
I’ve been using pop os for the past few months and I’ve fallen in love with its snapping window manager.
I have a 4K screen plus the laptop (xps 13).
I can have two browsers open, then my ide. And then terminal on the laptop screen.
And I can easily slide the divider between the ide and browsers as necessary based on what requires the most space at the time.
Only issues I’ve run into is being able to move multiple stacked windows to a new location, all at once. I probably just haven’t found the right shortcut.
It’s not exactly what you’re talking about, as the browsers are independent, but I’d be keen to see new browsing options like that.
It works nicely. The only thing that I haven't automated yet is that I have a rather specific workspace layout on my 4k screen and converting it from/to a laptop-screen workspace when unplugged takes a few steps.
Yes, plugging and unplugging is a major pain. I often find my windows re-appear on the wrong screen. And sometimes the wrong desktop… which is weird.
That's such a wasted design opportunity - give the users freedom in using a proper text editing tool instead of whatever awfulness the OS designers got stuck in decade(s) ago
But there are many other minimal UI browsers as well as Firefox that support no tabs.
I’ve been using qutebrowser which doesn’t have much of a UI since it is vim based
I'm using Firefox with a custom userChrome.css:
#TabsToolbar { visibility: collapse !important; }
Works quite ok but I cannot disable opening tabs completely in Firefox.
It's so frustrating to yearn for basic features in VSCode only to be ignored for years. For example, on macOS, a good amount of space is wasted because we can't hide the menu/title bar. We can't customize tabs either. No vertical tabs like Edge. No tabs height customization. It's either their way or the highway.
A gripe with Brave: Why doesn't the mouse-over feature for the vertical tabs doesn't work if the cursor is at the very left of the screen? And why can't we move the vertical bar to the right side of screen?
What is a "basic feature" to you is apparently not that to most people, certainly not to me. Just how important could it be to resize the tab height? And what would vertical tabs do that the open editors panel doesn't? I also don't follow regarding the menu bar -- that's the way all apps behave on MacOS? You can put it into fullscreen mode if you want.
It was possible with extensions like titleless and monkey patch, but Microsoft did something recently that made these extensions not work on newer versions.
What annoys me more is that stupid minimap that somehow has become an enabled by default "feature" on modern editors.
VS Code has a vertical documentlist, and if you want different styling, you can build an extension for this. No reason to have a duplicate feature out-of-the-box.
Emacs served as an IDE with tabbed window and pie menus, for interactively editing, viewing, and navigating HyperTIES markup language documents, graphics, and interactive PostScript "applets".
HyperTIES browser and Gosling Emacs authoring tool with pie menus on the NeWS window system
https://en.wikipedia.org/wiki/Tab_(interface)#/media/File:Hy...
>HyperTIES is an early hypermedia browser developed under the direction of Dr. Ben Shneiderman at the University of Maryland Human Computer Interaction Lab. This screen snapshot shows the HyperTIES authoring tool (built with UniPress's Gosling Emacs text editor, written in MockLisp) and browser (built with the NeWS window system, written in PostScript, C and Forth). The tabbed windows and pie menu reusable components were developed by Don Hopkins, who also developed the NeWS Emacs (NeMACS) and HyperTIES user interfaces. (Sorry about the quality -- this is a scan of an old screen dump printed by a laser printer.)
Emacs provides the pie menus you see popped up in the illustration (Articulate, Edit, New (Storyboard, Link, Picture, Target), Define) that control the HyperTIES browser from the custom text editing mode of HyperTIES storyboards (like web pages), which the HyperTIES browser (in the background, which emacs controls in a sub-process) formats and displays. HyperTIES also uses pie menus for navigation and in interactive "applets" programmed in PostScript.
[*] https://www.haiku-os.org/docs/userguide/en/GUI.html#stack-ti...
For me, it was the pinnacle of browser UI. Everything that came after that (including of course later iterations of Opera, which removed the MDI) has been considerably worse.
Perhaps a bit "bloated" for its time, but it was always pretty sleek to use. In fact I don't exactly remember why it never became mainstream. Maybe it had too many quirks or lagged behind others in terms of the new features, which... isn't entirely its own fault.
Looking at it now, it seems to have an identity crisis now. It looks like it has Whatsapp integration, among other things, which is the absolute last thing I'd ever want my browser to have an integration with.
The funny thing is that even though it included a lot of features I didn't use (for example, I never used the email client, not because it was bad, but I didn't use POP3/IMAP in general during that period), it was still much more efficient than all competitors in terms of speed, memory usage and even download size (at some point it boasted to be the only browser that fit in a floppy disk, although of course not for long).
I think the reason why it never became mainstream is that it was a paid product for a long time, while all other browsers were free. It eventually became free, but by then, competitors were too entrenched.
I also dislike Whatsapp but depending on country, it might be a necessary evil. In Spain for example, not having Whatsapp practically means forgoing any socialization with non-nerds. It's so ingrained in daily life that being without it is almost unthinkable for most people. Anyway, the current Opera doesn't have almost anything in common with the original one. Different engine, company, team, vision and even continent (owned by a Chinese company), only the brand and a thin sliver of identity remains.
(The sad thing is that I use it, because I still find it to be the least bad option for my needs...).
Also for a long time one of their main marketing points was that it had really small binary size so you could download it fast. They really spent a lot of engineering in making it performant
It's always worrying (and intriguing) when a small upstart decides to go closed-source when essentially the entire market is open-source.
Opera was sold to a Chinese company in the mid-10s and introduced suspicious stuff like a built-in free VPN. It is basically ignored nowadays.
The original CEO started Vivaldi, which is an excellent browser in terms of features - tiling tabs [0] were a favourite of mine. Unfortunately it is closed-source and chatty [1], but I still like on devices where privacy is not a concern.
like you can have multiple windows side by side, so what's the benefit of panes?
Yep. That is exactly how I think about it as well.
The browser and the IDE are effectively the same metaphor of a "super-app", just different security assumptions about where the information resides, how much it can be trusted and what can be done with it, how active the user input etc. In systems such as Firefox OS or ChromeOs the boundaries dissolve further.
Thinking about open source desktops and their application ecosystems, instead of countless independent efforts that waste precious talent in incompatible replication there could be some sort of architecture where lower level apps (editors, file/tab/bookmark/tag managers, shells, webview or spreadsheet renderers etc) could be recombined in various ways in the browser/IDE (or run as standalone apps).
KDE has allowed grouping windows as tabs, but that never really took off. There's a vast amount of tiling WMs, but none of them are truly popular, and I also don't want to open a terminal, or worse, emacs, to deal with wifi/bluetooth/thumbdrives just to showoff how unnecessarily awkward some things get to be when you don't run some mainstream desktop.
Run the web browser directly on the hardware, and implement the desktop window manager with that, in a way that the whole system is a scriptable integrated development environment. Then it's easy to implement tabbed windows, pie menus, and user-editable HyperCard-like interfaces.
Here's a big step in the right direction of supporting pie menus on the desktop:
Simon Schneegans's "Kando" project aims to implement cross-platform pie menus on the desktop. Simon implemented the beautiful "Pie Fly" Gnome shell extension and WYSIWYG pie menu editor, so I am really looking forward to what he does with other desktop interfaces!
Introducing: Kando:
https://ko-fi.com/post/Introducing-Ken-Do-L3L7L0FQ2
https://github.com/kando-menu/kando
>Kando will be a pie menu for the desktop. It will be highly customizable and will allow you to create your own menus and actions. For instance, you can use it to control your music player, to open your favorite websites or to simulate shortcuts. It will be available for Windows, Linux and maybe macOS.
Fly-Pie:
https://github.com/Schneegans/Fly-Pie
>Fly-Pie is an extension for GNOME Shell which lets you open marking menus via keyboard shortcuts. And — to the best of my knowledge — it is the first GNOME Shell extension with achievements!
>You can use it to launch applications, simulate hotkeys, open URLs and much more. It features a continuous learning curve which lets you gradually lift-off from a grumpie menu rookie to a snappie menu pielot. (You got it? Like pilot, but with a ). Once you opened a marking menu, you can seamlessly transition between three alternative selection modes:
>Point-and-Click: Select items by clicking on them or anywhere in the corresponding wedges.
>Marking-Mode: Select items by drawing gestures. To do this, click anywhere and drag your mouse. Pausing or making a turn selects the currently dragged item.
>Turbo-Mode: You can also "draw" gestures while holding Ctrl, Shift, or Alt without having to press your mouse button! This is especially useful when you opened the menu with a shortcut involving such a modifier.
Fly-Pie 7: GNOME Shell 40+ and a new WYSIWYG Menu Editor!:
https://www.youtube.com/watch?v=sRT3O9-H5Xs
Fly-Pie 10: A new Clipboard Menu, proper touch support & much more!:
https://www.youtube.com/watch?v=BGXtckqhEIk
I've written about reinventing scriptable HyperCard-like window managers with pie menus and tabbed windows before:
SimCity, Cellular Automata, and Happy Tool for HyperLook (nee HyperNeWS (nee GoodNeWS)):
https://donhopkins.medium.com/hyperlook-nee-hypernews-nee-go...
https://news.ycombinator.com/item?id=13817649
>At Sun we experimented with implementing an X11 window manager in NeWS. We didn't have transparency at the time (1992), but we did support shaped windows!
>The NeWS window manager supported cool stuff (for both X11 and NeWS windows!) like rooms, virtual scrolling desktops, tabbed windows, pie menus, was easily extensible and deeply customisable in PostScript, and ran locally in the window server so it could respond instantly to input events, lock the input queue and provide feedback and manipulate windows immediately without causing any context switches or dealing with asynchronous locking, unlocking and event handling. You'd never lose a keystroke or click when switching between applications, for example.
[...]
And here's how I think you should design a programmable "window manager" these days -- but it would be much more than just a window manager! It would be great for integrating legacy desktop and mobile applications into VR, for example!
>aQuery -- Like jQuery for Accessibility
http://donhopkins.com/mediawiki/index.php/AQuery
>Don asks Peter Korn: Hey I would love to bounce an idea off of you! I didn't realize how much work you've done in accessibility.
>There is a window manager for the Mac called Slate, that is extensible in JavaScript -- it makes a hidden WebView and uses its JS interpreter by extending it with some interfaces to the app to do window management, using the Mac Accessibility API.
>So I wanted to make pie menus for it, and thought of a good approach: make the hidden WebView not so hidden, but in the topmost layer of windows, covering all the screens, with a transparent background, that shows the desktop through anywhere you don't draw html.
>Then just make pie menus with JavaScript, which I've done. Works like a charm!
>THEN the next step I would like to do is this:
>aQuery -- like jQuery, but for selecting, querying and manipulating Mac app user interfaces via the Accessibility framework and protocols.
>So you can write jQuery-like selectors that search for and select Accessibility objects, and then it provides a convenient high level API for doing all kinds of stuff with them. So you can write higher level plugin widgets with aQuery that use HTML with jQuery, or even other types of user interfaces like voice recognition/synthesis, video tracking, augmented reality, web services, etc!
>For example, I want to click on a window and it will dynamically configure jQuery Pie Menus with the commands in the menu of a live Mac app. Or make a hypercard-like user interface builder that lets people drag buttons or commands out of Mac apps into their own stacks, and make special purpose simplified guis for controlling and integrating Mac apps.
>Does that sound crazy? I think it just might work! Implement the aQuery "selector engine" and heavy lifting in Objective C so that it runs really fast, and presents a nice high level useful interface to JavaScript.
[...]
https://news.ycombinator.com/item?id=29105919
>>Would you mind to share your opinion on Wayland with us?
>Thanks for asking! Hold my bong. ;) [lots of opinions omitted, see link above...]
https://news.ycombinator.com/item?id=22829690
>>Simula: A VR window manager for Linux [...]
>Soon after the invention of the movie camera, there was a "genera" of films that consisted of nothing but pointing a movie camera at a stage, and filming a play in one shot.
>That's the classic example of using a new technology to emulate an old technology, without taking advantage of the unique advantages of the new technology, before the grammar and language of film had been invented.
>Simply projecting desktop user interfaces designed for flat 2D screens and mice into VR is still in the "novelty show" age, like filming staged plays written for a theater, without any editing, shots, or film grammar.
>VR window managers are just a stop-gap backwards-compatibility bridge, while people work on inventing a grammar and language of interactive VR and AR user interfaces, and re-implement all the desktop and mobile applications from the ground up so they're not merely usable but actually enjoyable and aesthetically pleasing to use in VR.
>The current definition of "window manager," especially as it applies to X-Windows desktops, tightly constrains how we think and what we expect of user interface and application design. We need something much more flexible and extensible. Unfortunately X-Windows decades ago rejected the crucially important ideas behind NeWS and AJAX, that the window manager should be open-ended and dynamically extensible with downloadable code, which is the key to making efficient, deeply integrated user interfaces.
>For example, the "Dragon Naturally Speaking" speech synthesis and recognition system has "dragonfly", a Python-based "speech manager" that is capable of hooking into existing unmodified desktop applications, and scripting custom speech based user interfaces.
>Another more ambitious example is Morgan Dixon's work on Prefab, that screen-scrapes the pixels of desktop apps, and uses pattern recognition and composition to remix and modify them. This is like cinematographers finally discovering they can edit films, cut and splice shots together, overlay text and graphics and pictures-in-pictures and adjacent frames. But Prefab isn't built around a scripting language like dragonfly, NeWS or AJAX.
>Here's some stuff I've written about the direction that user interfaces should take to move beyond the antique notion of "window managers", and enables much deeper integration and accessibility and alternative input and output methods.
https://news.ycombinator.com/item?id=14182061
>Glad to see people are still making better window managers! [...] I think extensibility and accessibility are extremely important for window managers. [...] I'd like to take that idea a lot further, so I wrote up some ideas about programming window management, accessibility, screen scraping, pattern recognition and automation in JavaScript. [...] Check out Morgan Dixon's and James Fogarty's amazing work on user interface customization with Prefab, about which they've published several excellent CHI papers: [...]
>Imagine if every interface was open source. Any of us could modify the software we use every day. Unfortunately, we don't have the source.
>Prefab realizes this vision using only the pixels of everyday interfaces. This video shows the use of Prefab to add new functionality to Adobe Photoshop, Apple iTunes, and Microsoft Windows Media Player. Prefab represents a new approach to deploying HCI research in everyday software, and is also the first step toward a future where anybody can modify any interface.
https://news.ycombinator.com/item?id=18797818
>Here are some other interesting things related to scriptable window management and accessibility to check out: aQuery -- Like jQuery for Accessibility
https://web.archive.org/web/20180826132551/http://donhopkins...
>It would also be great to flesh out the accessibility and speech recognition APIs, and make it possible to write all kinds of intelligent application automation and integration scripts, bots, with nice HTML user interfaces in JavaScript. Take a look at what Dragon Naturally Speaking has done with Python:
https://github.com/t4ngo/dragonfly
>Morgan Dixon's work with Prefab is brilliant.
>I would like to discuss how we could integrate Prefab with a Javascriptable, extensible API like aQuery, so you could write "selectors" that used prefab's pattern recognition techniques, bind those to JavaScript event handlers, and write high level widgets on top of that in JavaScript, and implement the graphical overlays and gui enhancements in HTML/Canvas/etc like I've done with Slate and the WebView overlay.
BTW, I was a TST user for many years, and recently switched to Sidebery, which seems to do the same and more, but is a bit more polished.
#main-window #TabsToolbar {
height: 40px !important;
overflow: hidden;
transition: height 0.2s ease-in 0s !important;
}
#main-window[titlepreface*=" "] #TabsToolbar {
height: 0 !important;
min-height: 0 !important;
}
#main-window[titlepreface*=" "] #tabbrowser-tabs {
position: fixed;
z-index: 0 !important;
}
#main-window[titlepreface*=" "] .tab-stack {
visibility: hidden;
}
#main-window[titlepreface*=" "] #toolbar {
min-height: 0;
}
#main-window[titlepreface*=" "] #sidebar-header {
visibility: hidden;
height: 0px;
padding: 0px !important;
border: 0px !important;
}
#main-window[titlepreface*=" "] #titlebar {
visibility: hidden;
height: 0px;
}
To make it work only when Sidebery is open, make sure you add a preface value in the Sidebery settings and use the same value in the css above; in my case I just use an invisible character. Couple it with Ctrl-E keybind to toggle the Sidebery panel, and it's been a big quality of life improvement for me.Doesn't really match my experience. In which ways is it more polished?
TST remains great, though, very versatile and extensible.
In the default setting, there is OS title bar, then a address+icon bar, then the tab bar.
After installing sidebar tabs, you can remove the tab bar with some css, which saves about 5% of the vertical screen space.
That's on the right track, but going too far. 16:10 or 3:2 is much more reasonable.
The idea of using 16:9 screens for work needs to die in a fire.
That said, working on a web project right now, we _are_ ensuring it looks good when maximised on ultra wide monitors, because we figure people might actually do that. But I'm with you there, for most web content it's ridiculous.
Sat next to it is a 32" 2560x1440 unit (they have near identical pixel pitch, so I don't have to worry about oddities like differential scaling between screens) that most of the time is split into two halves or ⅔+⅓ (under windows, the FancyZones util in PowerToys is handy for this).
I liked the arrangement so much at home that I've replicated it at my own expense in the office.
Honestly, that's not the main selling point of vertical tabs for me. Horizontal tabs don't scale for more than a dozen or so, but vertical tabs do. The "wasted" horizontal space is useless for reading most page, but displays enough data for practical navigation, and the vertical organization allows more-developed vertical scrolling technologies to be used with the tab list (e.g. scroll wheels).
Firefox also lets you scroll the tabs horizontally. Which I prefer to Brave's approach of simply not displaying the last tabs in the bar if it's too many, which means newly opened tabs simply never show up while the others are shrunk so far they become difficult to hit with the cursor.
And since horizontal space is cheap in most websites, the latter part is less of an issue (though you still don't need it to be massive)
I can use 2 windows side by side and the pane just eats horizontal padding on most sites because narrow columns are prettier and easier to read.
I used OmniWeb as my main browser for many years, right up until Firebug and Firefox became the preferred development environment. Great browser, a lot of great UI ideas out of that shop.
I moved on to Safari after it died, but I missed vertical tabs dearly and still do. Hopefully this idea catches on well enough for the Safari team to finally steal it.
https://www.omnigroup.com/more
I only tried it on a few websites but it worked remarkably well.
I paid for that browser and I still would.
My setup: https://i.imgur.com/sZ8zdol.png
This has some quirks because of the limitations a browser extension has, but I now much prefer to just use keyboard shortcuts and search to jump to tabs.
Safari introduced “tab groups” a while back, which to me is an insane mess of complexity. When I think about it though they’re just folders and each tab is a bookmark/favorite.
The vertical tabs in Brave remind me of bookmarks/favorites too.
As for tab groups, I could never get used to them, but I do use vertical tabs and find them quite useful.
Arc has "pinned tabs", but not "bookmarks". While they can be used similarly, I find it quite annoying to use the search to pull something out of my "bookmarks", only to have it open a directory hierarchy eight levels deep when I switch to it.
Likewise, if I navigate away from the page on the pinned tab, I lose my "bookmark".
These are tabs that I don’t want to close as they have context and sometimes ongoing edits. It’s a bit like having multiple windows each with tabs but this keeps it together in one window and makes it easier to manager.
Without this, I would be facing 50-75 tabs and trying to figure out which ones were related to the project I needed to work on at the current time.
There are some others, but I haven't tried a wide range of them. Panorama does what I need.
What counts isn't some abstract storage concept but the UI and UX to manage them. Bookmarks are this drawer in your basement where you have to actively spend energy to find them. Tree tabs are self organizing. How they are are stored is irrelevant to me.
The reason I like it is that he’s unified tabs and bookmarks almost, it’s a great UX that looks like some things you might have seen but still feels different.
He’s also got wicked design sense — but I’m biased so. I also feel like I’m doing him a disservice — he’s got one of those silly lifetime deals going right now.
What page were you on where you saw that? Were you not able to load the page itself?
If you wouldn't mind opening up the browser console, I'd love to know what went wrong.
https://twitter.com/PascalPixel/status/1585224743480721408
I've passed it on, hopefully he'll have the website updated with a screenshot in like... 10 mins
Here's a screenshot of the browser: https://twitter.com/PascalPixel/status/1585224743480721408
No screenshots is huge though. That should be front an center for something that is all about the UI experience. Why would I commit $100 dollars to something I can't see.
https://twitter.com/PascalPixel/status/1585224743480721408
I'm talking to pascal right now and urging him to put a screenshot up!
Needs extension support before it's really viable though.
- I spend time researching X, have a few pages open for that, get bored with it, want to continue in a few days.
- I work on X, which has a few related tabs open, and I need to switch to Y for a bit.
- There's a long-term thing I'm working on and off.
- Something I found and want to look at later; "bookmarks-light" (bookmarks might as well be /dev/null for me).
* Convenience
* Tooling
It's more convenient to keep tabs open. With Tree Style Tabs on Firefox and Orion's vertical tabs I can retain the relationship. The browser generally keeps it cached so even if the site goes offline I can read what I need to. If I have a form partially entered, I can resume it. If the page has infinite scroll but doesn't update the URL, I can stay where I was. Some sites tie resources to a particular session so resuming from a bookmark won't get you to the resource anyway.But, I can also find things faster if they're on a pile on my desk than I can if they're put away in a drawer so I'm sure it's different for everyone.
As for tooling, I think browsers just aren't very good at bookmark management. I find the sidebar for bookmarks borderline useless, but a tree of tabs in the same space is quite efficient for me. The bookmark manager isn't much better. We can use folders, but not really have the rich links the web was designed for. I often have both the HN discussion and article open with either a parent-child or sibling relationship in my vertical tabs. That's not easily replicated with bookmarks.
The other tooling issue is tab management isn't great. Chrome's shrinking tabs is terrible HCI; you can't read them and they become harder to click. Finding a tab can be frustrating. It's often easier to open a new tab to complete a task than go hunting for the one I want. Pinning tabs doesn't work great with multiple windows and seeing just the favicon isn't super helpful if you need to pin two pages from the same domain.
Between the tabs I keep open because that's how my brain works best and between tabs I get stuck with because browsers haven't provided better tooling, it's easy to grow into the hundreds and then periodically cull them.
And the content of tabs is also cached/loaded unlike with bookmarks
I guess the last part is fixed in later chromium by hibernating tabs now?
But as with you, my muscle memory gets in the way.
The primary input mechanism for dealing with a large amount of "list entries" in any GUI software, nowadays is scrolling. While scrolling can be implemented in horizontal tabs, browsers prevented it from being used efficiently. Tabs all have to fit on that bar, and if they don't, for some reason you couldn't scroll but had to click little buttons, or if you could scoll, it wouldve been a bad UX, since tabs horizontal scrolling goes too fast for the user, or takes too long.
Vertical tabs. Nice. From now on, any browser not offering this feature, shouldn't even bother applying. Nicely done Brave!
Been a thing for years in old Opera first
Firefox has extensions for it
Edge and Vivaldi has it native
Vertical tabs solve a core issue in horizontal tabs. Tabs are inherently 2D: the number of tabs vs the length of their titles. Horizontal tabs can scale only to one dimension. You can choose to either see many of your tabs at once, but not be able to read any of the titles, or be able to read the titles but have to scroll absurd distances just to view what tabs are open.
Vertical tabs give you a 2-dimensional view of your tabs. You can see many of your tabs and be able to read as much of the titles you want by scaling the horizontal size of the area independently.
I think it's brilliant. I also don't see how browsers could "fix" horizontal tabs without resorting to taking away valuable vertical space from the content that is the primary purpose of browsers.
You should be able to easily drag any tab to the top, bottom, left, or right edge of the window, and pop up pie menus on the tab to perform window management (and custom) commands on the tab or all tabs on the same edge, including covered-up windows.
For example: Lots of "todo" tabs on the left, "done" tabs on the right, a few "in progress" tabs along the top, "problem" tabs along the bottom, so you can drag tabs between "todo" to "in progress", "problem", or "done", or select "close all left tabs" from a pie menu to clear out the "done" tasks, to easily manage your tasks with tabs.
You could even partition edges into different groups of tabs, if you wanted. And manage multiple tiled windows inside the frame. A pie menu on the tab will let you open it up to full frame, split to bottom, split to top (with the obvious directions).
Any sub-dialogs a window opens up could have their tabs laid out in a stack along a certain edge from a certain corner.
You could designate edges (or sections of adjacent edges corresponding to tiled windows) to show the tabs of sub-windows of the selected window (to implement tree browsers).
The app or document in the frame should be able to export custom commands that appear on the tab pie menu, so you can do stuff with the window without bringing it to the top or disturbing the currently displayed windows.
The point is that the user should be able to decide what tabs to put where for what reason, not that one edge is the right edge and all other edges or wrong, or using more than one edge at a time is wrong.
With regular horizontal tabs you either squeeze all tabs to fit the window width, in which case you stop being able to read page titles at some point. Or you have a horizontal scroll on the tab bar which also means you can only read so many titles on screen (probably fewer) before needing to scroll.
The vertical tabs switch this up by being able to show a larger number of tab titles before you have to scroll down. Of course this depends on the width of your vertical tab sidebar but having word wrap or configurable height on horizontal tab bars isn't ever presented as an option so can't compare.
Another clue to understanding my preference was when I realised I actually really like being able to have multiple rows of horizontal tabs vs a horizontally scrolling tab bar. So I think it just came down to the density of information visually available before having to do any scrolling.
I do think it all just comes down to personal preferences and muscle memory and individual use cases (for example, some people like having 50+ tabs open, others don't). So I am very hesitant to call one approach better. I just don't understand why we can't have both options more available everywhere.
So, looks like I’ll move to that when Apollo shuts down.
Works with Twitter too - I’m a noob smh.
*looks like I’m wrong- now not loading. Oh well.
Haven't seen an ad in... years. For crypto or otherwise.
Been using the browser for 2 years and yet to see an ad.
Most features in Brave are opt-in, not opt-out. I don't know why people think otherwise. This is not Chrome or Edge.
Besides, I'd rather have this level of adware than Chrome level of spyware.
It's also a lot better than any other mainstream browser out there. Firefox has tons of ads too and Chrome and Edge, let's not go there.
Why not go there? Because it shows Brave is adware and Chrome is not? What ads does Chrome have? Even to opt-in to?
Note that Brave's opt in dialog is itself an ad. After you dismiss it, the ad continues to live permanently in browser settings.
It had a major downside of putting browser chrome over the page area and hiding the URL. Over time the latter has become the default anyways but the former is still iffy. Safari approached this concept more recently, as the only browser I'm aware with this as an officially supported option, but put the URL bar directly in the tab, which is a bit more awkward to use. On Vivaldi there is the option to hide it but then activate it via a keyboard shortcut/gesture, which functions similarly but can cause extra switching between keyboard based navigation and mouse based navigation (the latter of which can be very hard to avoid). Because of the way Vivaldi is implemented it's always performed a lot worse than other Chromium based browsers for me as well. In Firefox there were several CSS hacks for this but it was constantly falling apart on updates so I gave up on it.
I guess the long story short is: as a very light tab user (1-8 throughout the day) I miss this old option in Chrom* greatly.
Otherwise, I would have kept using it - it was fast and energy efficient on my intel macbook, way better than chrome.
I also have to say - I hate when I have so many tabs open. It's basically a manifestation of my ADHD. I need to focus one thing at a time.
Quick Google result: https://github.com/brave/brave-browser/issues/5429
The GitHub issues that you linked also are closed. I followed the duplicates and they're all closed with comments mentioning that it's been fixed.
The ads and crypto stuff are also not exactly as simple to opt out as "literally disable it in the welcome screen when you first install" as one commenter enthusiastically mentioned.
All of it is definitely opt-in. Even Brave Rewards are disabled by default.
Arc does this, but they don't give you the URL bar. It may sound nitpicky (and it is) but I really want the hidden tab sidebar AND a visible URL bar. Here's hoping either Arc or Brave will make this an option.
Tree style tabs is the main reason I've used firefox since.
Tabs are really a bad design, maybe made some sense with 4:3 monitors but text was horizontal back then too.
The main problem I have now is that I have trouble finding old stuff because internet search keeps getting worse.
Bookmarks aren’t really a solution because they are not searchable, and I’m bad at predicting what I will want to re-read in 5-10 years.
https://piro.sakura.ne.jp/xul/_treestyletab.html.en#history
I am not sure if someone like Opera was earlier, but Arc is likely copying this.
OmniWeb 5.0, 2004: https://arstechnica.com/gadgets/2004/02/ow5/3/#tabs
edit: Started up a VM -- Opera 3 didnt have tabs at all, although it did already have an MDI.
The concept of “drawers” that OS X had at the time was well suited for this kind of thing, with some “free” (in terms of dev effort) flexibility of allowing the user to choose which edge they unfurled from. It’s too bad they fell out of style in favor of much more static sidebars.
Orion[1] is another recent MacOS browser that released before Arc in 2021 and has vertical tabs. Edge had vertical tabs as an experiment back in 2020[2] and is full feature now. Vivaldi has had vertical tabs since 2015[3]. It might not count since it's not built in, but Firefox has had vertical tab extensions since 2007[4].
[2] https://www.howtogeek.com/697986/how-to-enable-and-use-verti...
[3]https://www.maketecheasier.com/vertical-tabs-browsers/
[4]https://github.com/piroor/treestyletab/graphs/contributors
Brave has been the best innovation in browsers in recent years. A pleasure to use. Kudos to them and their users for putting up with all the hate.
(Sadly, I can't call Firefox all that mainstream today.)
The more I think about it — the more Arc reminds me of an IDE. A browser IDE of a kind.
Meanwhile Mozilla is showing signs of serious, systemic internal org issues, and no problem? [2]
It's pretty clear a user / privacy-first model is central to Brave's mission, so these drive-by comments griping loudly about minor, historical issues never feel intellectually compelling.
[1] https://twitter.com/BrendanEich/status/1269317625915400192
Meanwhile, they also fund novel privacy and security research [1], including preventing advanced fingerprinting. In essence, the maintain a patch set on top of Chromium (the open source base of Chrome, that Edge also builds on) which more convincingly respects user privacy, security, and choice[2][3][4]. See how much effort they put into keeping Brave Ads convincingly private [5].
Each of these is less intrusive than changes (to stay recent and relevant) include direct partnership for promotions [6].
Or to base beliefs on a series of news reports that sound bad, see a longer list [7], though it's quite noisy list.
[1]: https://brave.com/research/
[2]: https://github.com/brave/brave-browser/issues/14942
[3]: https://en.wikipedia.org/wiki/Federated_Learning_of_Cohorts
[4]: https://brave.com/why-brave-disables-floc/
[5]: https://support.brave.com/hc/en-us/articles/360026361072-Bra...
[6]: https://itsfoss.com/firefox-looking-glass-controversy/
[7]: https://chefkochblog.wordpress.com/2022/03/03/mozilla-histor...
(Not a user of the browser in question)
But Cmd+L+C is exactly the same number of sequential keypresses as Cmd+Shift+C. So I guess Firefox has this desirable behaviour covered!
HCIL Demo - HyperTIES Authoring with UniPress Emacs on NeWS:
https://www.youtube.com/watch?v=hhmU2B79EDU
>Demo of UniPress Emacs based HyperTIES authoring tool, by Don Hopkins, at the University of Maryland Human Computer Interaction Lab.
HyperTIES discussions from Hacker News:
https://donhopkins.medium.com/hyperties-discussions-from-hac...
I later implemented pie menus and tabbed windows for the NeWS Toolkit (TNT) "Open Look" window manager in 1990 for Sun OpenWindows (X11/NeWS), that let you drag the tabs around to any edge of the window, and wrap all your windows in tabbed frames, even including X11 windows!
NeWS Tab Window Demo (This video may not play in some regions due to copyrighted music):
https://www.youtube.com/watch?v=tMcmQk-q0k4
>Demo of the Pie Menu Tab Window Manager for The NeWS Toolkit 2.0. Developed and demonstrated by Don Hopkins.
Object oriented PostScript source code for NeWS TNT 2.0 pie menus and tabbed windows:
https://donhopkins.com/home/archive/NeWS/win/pie.ps
https://donhopkins.com/home/archive/NeWS/win/tab.ps
Tabbed window (with pop-up pie menus on the tabs) are also great for representing PostScript object stuck onto a "stack":
PSIBER Space Deck Demo:
https://www.youtube.com/watch?v=iuC_DDgQmsM
The Shape of PSIBER Space: PostScript Interactive Bug Eradication Routines — October 1989:
https://donhopkins.medium.com/the-shape-of-psiber-space-octo...
Tabbed Windows - History:
https://en.wikipedia.org/wiki/Tab_(interface)#History
>Don Hopkins developed and released several versions of tabbed window frames for the NeWS window system as free software, which the window manager applied to all NeWS applications, and enabled users to drag the tabs around to any edge of the window.[5]
>The NeWS version of UniPress's Gosling Emacs text editor was another early product with multiple tabbed windows in 1988.[6] It was used to develop an authoring tool for Ben Shneiderman's hypermedia browser HyperTIES (the NeWS workstation version of The Interactive Encyclopedia System), in 1988 at the University of Maryland Human-Computer Interaction Lab.[7][8] HyperTIES also supported pie menus for managing windows and browsing hypermedia documents with PostScript applets.
HyperTIES browser and Gosling Emacs authoring tool with pie menus on the NeWS window system:
https://en.wikipedia.org/wiki/Tab_(interface)#/media/File:Hy...
>HyperTIES is an early hypermedia browser developed under the direction of Dr. Ben Shneiderman at the University of Maryland Human Computer Interaction Lab. This screen snapshot shows the HyperTIES authoring tool (built with UniPress's Gosling Emacs text editor, written in MockLisp) and browser (built with the NeWS window system, written in PostScript, C and Forth). The tabbed windows and pie menu reusable components were developed by Don Hopkins, who also developed the NeWS Emacs (NeMACS) and HyperTIES user interfaces. (Sorry about the quality -- this is a scan of an old screen dump printed by a laser printer.)
I jest, but I don't think I get what you are implying. What is the difference between this fantasy name and any other that is also an existing noun?
For once can we just skip the inevitable discussion that takes place in every single brave thread?
Thanks and sorry - I didn't mean to start a thread that is not useful for most people
* cryptocurrency related bits, relation to BAT token
* Fiasco where they collected earnings on behalf of creators without their consent/knowledge/optin
* Run by Brendan Eich who some people don’t like because he created javascript, and/or is not supportive of gay people in some ways
I am sure I am forgetting some
Not sure I follow.
I used Firefox for 20 years but had to switch to a Chromium browser due to performance. Went with Brave, seemed to be the best of the bunch.
I've been happy with it. What's the problem with the name?