http://kb.mozillazine.org/index.php?title=UserChrome.css
Here's a few simple examples:
https://github.com/Timvde/UserChrome-Tweaks/tree/master/tabs
And a more thorough one:
https://old.reddit.com/r/FirefoxCSS/comments/7emhsq/my_compa...
Do you use vim-like extensions, but hate how surface-level they become due to hard WebExtension limitations? Pining to recapture the days of Pentadactyl? Qutebrowser is built for vim-like navigation from the ground up:
* Hate getting stuck on about//:* / chrome://* pages? Every single page in qutebrowser works with your keybindings!
* Hate PDFs for the same reason? Qutebrowser will read PDFs and keeps your keybindings there, too!
* Wish you could have a dotfile configuration for your browser? Qutebrowser (optionally) does dotfiles (and they're Python!)
* Wish you had a real EX mode? Qutebrowser has one and it does not disappoint in terms of customization/functionality. It's actually the linchpin of the the entire UX, much like the Omnibar is for Chrome.
* Wish you had a keyboard-driven text selection mode? Qutebrowser has one!
* Hate file pickers forcing you to reach for the mouse? Qutebrowser implements its own keyboard-driven file picker (and it's actually really good!)
Have you considered other browsers in the past, but passed them up due to a lack of extension support? Well... Qutebrowser can't handle WebExtensions, but it does provide most features you would miss:
* Dark Mode? It exposes the same performant, engine-level dark mode that Chrome does
* Adblock? Qutebrowser supports hostlist-based adblocking (with auto-update) OR, if you want real Adblock, you can install jblock for qutebrowser, which is comparable functionality-wise to "uBlock"-type extensions (yes, including Youtube)
* Userscripts? Qutebrowser supports loading userscripts and is mostly compatible with the GreaseMonkey 3/4 APIs. This covers what most "minor" extensions (e.g. HTTPS Everywhere / Old Reddit redirectors / UI tweaks) can do
* Custom CSS? Most "userstyle"-type websites package a "Greasemonkey" version that will work just fine with the previously remarked userscript functionality
* Password management? Qutebrowser comes with scripting support that will allow you to interface with your desktop-side password manager. Out of the box, it comes pre-packaged with scripts for connecting to GNU pass, bitwarden, keepass, and lastpass.
As for adblocking, I wouldn't recommend jblock (it's rather buggy from what I've seen so far) - but a built-in adblocker based on Brave's Rust library is almost ready now: https://github.com/qutebrowser/qutebrowser/pull/5317
Of course, as always, thanks for the excellent software!
I'm not saying vim-like extensions aren't worth using, but they are inherently less capable due to hamstringing by WebExtension APIs. If anything, it's proof of how much work and care goes into them, since they have to fight the limitations of a framework not designed for this type of UI overhaul
To further illustrate: I primarily have an open Terminal+Tmux for editing on my main monitor. On my side, i have spacial but overlapping windows. They stick out a bit, such that it's primarily four tabs - left,up,right,down. For example my Slack is on the left tab, and i can always see my contact list, people typing to me, etc. My Browser is usually on the Up tab, as it allows me to see the browsers tabs themselves. I do the same with Zoom on the bottom, such that my Mic (mute/unmute) is always visible. And etc.
This arrangement perhaps isn't ideal, but it's better than a tile for me because in a tile, i lose so much real-estate that the window becomes near useless. I can't shrink Slack to 1/4 of my Monitor, it's got too many boarders/etc. Same goes for my Browser, most sites have non-collapsing sidebars and etc, a tiny 1/4 window is useless.
This method of spacial layout obscures ~90% of my windows but leaves some of it always visible. In some cases that's very useful. But this is something i manage through the day, and a WM to automate this positioning would be amazing.
Check out 2.2. Changing the container layout here: https://i3wm.org/docs/userguide.html
Example:
- Start i3 in tabbed mode
- Open a window for coding
- Open a browser to search for some coding question. It opens in a new i3 tab, filling the screen like it would in a non-tiling WM
- Open a terminal to try the sample code (new i3 tab)
- Google the error message you get (new i3 tab)
- Use rofi to search for "code" and press Enter. Your coding window tab is activated and the coding window fills the screen
- Realizing the sample code you found would be useful here, along with the test terminal, tile those windows alongside your coding window. Now you can quickly refer to them and switch between them with spatial keybindings
- Switch back to the error message browser using rofi to check something. It's not part of your core workflow right now, so don't worry about tiling it
That's probably obvious to anyone who's used a tiling WM for any length of time, but tiling was daunting to me until it clicked. I spent too much time thinking about optimal window arrangements. Thinking of tiling as an optional finishing touch rather than a focal point made it much more useful/practical.