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.

  • auth
    4·
    3 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.

    • www-gem
      4·
      3 months ago

      Tiling WM are more than screen splitters. It’s difficult to apprehend without trying it. A friend of mine had the same reasoning before actually trying one. Now he couldn’t go back. Although, like everything else, tiling WM are not for everyone and that’s why there’re other options :)

      • auth
        1·
        3 months ago

        there was too many bugs in tiling WM last time i tried… which one do you use?

        • www-gem
          4·
          3 months ago

          I’ve been through awesomewm, i3, and dwm. Now I’m using bspwm. Each one has its own specificities and is more or less easy to familiarized with.

    • Pantherina@feddit.de
      2·
      3 months ago

      COSMIC is getting “fancy zone” snapping at the moment it seems (community efford)

      COSMIC already has tabbing/stacking windows which is so cool, as I can finally ditch Konsole for Alacritty (if I manage profiles for distroboxes and color profiles etc).

      I kinda try to get used to autotiling but its strange as fuck.