Design of GitLab is a pain

A while back GitLab changed design (again) and put the content scrollbar 10 pixels away from the site edge. This resulted in me finding a workaround to push the content and the scrollbar to the edge. I went with a custom CSS hack:

body div.layout-page.page-with-super-sidebar
{
    padding: 0px !important;
    column-gap: 0px !important;
}

This worked fine for a while, I do not remember for how long as I forgot when I solved the issue. The GitLab broke again, someone decided to add a border around the content. This was probably done because the content was now “floating” on a page and someone wanted it to look “nicer” with a border. Whatever the reason, now there is a border to worry about. So a new addition to my workaround was needed.

body div.layout-page.page-with-super-sidebar
{
    padding: 0px !important;
    column-gap: 0px !important;
}
body div.layout-page.page-with-super-sidebar div.panels-container
{
    border: none !important;
}

I have this in my custom style in Falkon, it can be adapted to the custom rules of uBlock Origin as well. I will leave that to someone else.

This workaround improves the overall usability of GitLab for me as when I use the mouse, I want to go to the edge of the screen or window (some window manager allow to “pause” the mouse at the window edge) and click and/or drag to move the scrollbar. The modern design used by default on GitLab does not allow me to do so and forces me to do small mouse movements.

I am of the opinion that computers should make my work easier and more comfortable, so this modern desing is a bug.

Articles from blogs I follow:

There's no point at which turning your brain off will work

In early 2025, I started seeing people turn off their brain as they use LLMs1. They would have an LLM take an action (summarize text, write some code, etc.), and just assume that it worked2. This generally didn't work in early 2025 and the result was …

via danluu.com September 18, 2026

Stop telling people to sanitize user input

Whether you're dealing with a web application or some other application, all user input should always be considered "hostile" and "dangerous", but you should not just universally sanitize user input.

via Unix Digest - Articles March 7, 2026

GPG Update 2026

A recent toot of mine got the response “friends don’t let friends use GPG” which, I suppose, is true enough. It certainly isn’t the attestation-friendly thing to use, and the opsec failures that are so easy with GPG-encrypted mail make it a hazard there. …

via [bobulate] February 3, 2026

Generated by openring