People talk about the 'good old days' of the web, but boy, in a multi-tab environment it stucks to try and read something that doesn't put any effort at all into side margins.
Side note: Dan Luu claims[0][1] that there's no readability advantage to narrow line width. I haven't really looked into it, but in my experience it feels like he's very wrong.
[0]: https://danluu.com/slow-device/ [Appendix: this site vs. sites that don't work on slow devices or slow connections]
Reading the wikipedia references show me that this is well studied and sourced.
Academic sources for his argument either dont exist or are so rare even he can't find them.
IOW, it's a post hoc rationalisation from him.
javascript:(function(){var newSS, styles='body { width: 800px ! important; margin: auto !important } '; if(document.createStyleSheet) { document.createStyleSheet("javascript:'"+styles+"'"); } else { newSS=document.createElement('link'); newSS.rel='stylesheet'; newSS.href='data:text/css,'+escape(styles); document.getElementsByTagName("head")[0].appendChild(newSS); } })();
You can write this feature as a userscript and then publish it to greasyfork
For example, older monitors had less pixels, so it's likely that the wrapping was sensible in older monitor/browser configs.
To say nothing of browser defaults being different, if this was pre-css, then the margins might have been baked into the default browser interpretation. In other words, pre-margin property, a webpage without margin didn't mean "this has no margin", in the sense that a modern webpage without margin specified would mean "DO NOT ADD MARGIN TO THIS!".
Also, reader mode was not suppressed by some naughty trick.
Unreal.
The real problem is our screens are the wrong shape. 16:9 is a stupid aspect ratio for a computer monitor if you work mostly with text. Square is probably the best. Using floating windows (like classic Mac OSX) is an option, but for some reason people like full screen windows these days. A tiling window manager is another option to effectively divide the screen up into better shaped areas. I tend to have 6 columns across 2 screens which works well.
Why? I also usually use it with three columns of text, and it works well at that aspect ratio.
What you really have to ask yourself is why 16:9 is a better choice than anything else. It wasn't picked because 3 16:27 columns is ideal for text. The main reason we have them is because it's easier for the screen manufacturers to have just one aspect ratio to deal with. With 16:9 we're forced to have three columns per screen, but what if I only need two? What if I want more lines of text per screen? Square seems like a much more obvious middle ground.
Not just that, but it was an average of aspect ratios considered for the aesthetic of video data. Not text presentation.
My browser tabs are on the left side of the screen and they are all written left to right. There is ample space on the sides of websites to fit this and show the entire tab title. Meanwhile, other people have tabs along the top of the screen that all show one or two letters followed by “...”.
My taskbar is on the right and consists entirely of icons. The only text on it is the date/time and that is also written normally and not rotated.
This is the setup that I was saying I don't understand the resistance against — not 90° rotated text. When people say “vertical tabs”, they are not talking about rotating the text.
It is a side effect of mobile devices -- Mobile-first design. When apps got popular, people decided that everything needed to be designed for mobile devices first, and adjusted for larger browsers screens later. So people started making everything tall and narrow. And said it was bad practice to do otherwise. Now people who learned UI design after those days often follow that idea. Personally, I am not a fan, but that is where it comes from.