In the image, these are not tabs. These are firefox windows, being rendered as tabs (and as stacks) by sway.

I just switched to sway, and found that browser tabs no longer make sense. They were designed in the UI dark ages to make up for how terrible Windows XP’s WM was. Now, though, sway can do tabs just as well as firefox can, and sometimes, even better. It is better to unify the management of all windows under a single WM, rather than this ad hoc mixture of the real, global WM, and a fake firefox-only (or terminal-only) WM. That way, all windows are managed with a single set of keyboard shortcuts.

I also found firefox’s toolbar to be way too thick.

So, I used userChrome.css to hide the tab bar and adjust the toolbar’s height:

/* Hide the tab bar. */
#TabsToolbar {
    visibility: collapse !important;
}

/* Adjust the toolbar height. */
#urlbar-container {
    --urlbar-container-height: var(--tbh) !important;
}
#urlbar {
    --urlbar-toolbar-height: var(--tbh) !important;
    --urlbar-height: var(--tbh) !important;
}
:root {
    --tbh: 26px !important; /* ToolBar Height. Adjust this one. */
    --toolbarbutton-inner-padding: calc((var(--tbh) - 16px)/2) !important;
    --toolbarbutton-outer-padding: 0px !important;
    --toolbar-start-end-padding: 0px !important;
    --urlbar-margin-inline: 0px !important;
}

Put this file at <profile root>/chrome/userChrome.css. You’ll probably have to make the chrome directory. Then, in about:config, set toolkit.legacyUserProfileCustomizations.stylesheets to true, to get firefox to read userChrome.css. Oh, and don’t forget to tell firefox to open new pages in new windows instead of new tabs.

I have also found it useful to map the firefox command to Super-C, so that I can make a new firefox window without needing to have some other firefox window already in focus.

I have also found it useful to keep an empty firefox window open in some unused workspace on its own, so that after I close what I didn’t realise was the last open firefox window, firefox does not close entirely.

  • matcha_addict@lemy.lol
    link
    fedilink
    arrow-up
    1
    ·
    8 months ago

    So is each Firefox tab a separate window with this design? And thus managed by sway as separate windows and tabbed accordingly?

  • stepanzak@iusearchlinux.fyi
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    You haven’t seen my Firefox with Sidebery extension and almost 300 tabs open, neatly organized into categories, tab stacks with three levels and folders :P I should clean it up some day

    • Lunya \ she/it@iusearchlinux.fyi
      link
      fedilink
      arrow-up
      1
      ·
      8 months ago

      You haven’t seen my Firefox with Sidebery extension and 544 tabs open, not even remotely organized into categories, no tab stacks with three levels and folders :P I should clean it up some day

  • Brickardo@feddit.nl
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    I think this is super inefficient if you happen to have more than maybe three tabs open. How long will it take me to reach to the file explorer I’ve also opened? Moreover, how long will it take me to find it…?

  • thejevans@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    I still find windows and tabs to be a useful way to have a nested organizational structure for web browsing. To solve the visual issue, I permanently hide the tab bar, and I use tree-style tabs with css to auto-hide the tab panel unless my cursor is all the way on the left side of the window. I also have the toolbar autohide unless my cursor is at the top of the window.

  • auth@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    8 months ago

    I like the idea of a tiling window manager but I found it about as effective to use a regular window manager like KDE or Gnome that allows you to snap windows to 1/4 or 1/2 the screen … Windows even does that.