17 ms·
That makes sense when (as in the old days) you have one window per web page, but most people these days have a single window (or a few) with lots of tabs inside
by ptx 7y ago
That makes sense when (as in the old days) you have one window per web page, but most people these days have a single window (or a few) with lots of tabs inside that window. You don't want to adapt the window to one particular site when the window is shared for many other sites (for which that site's comfortable size might not be a comfortable size).
- macleginn 7y agoIt's partly compensated for by the fact that the pages plays well with the read-mode plugin in Firefox.
- psychometry 7y agoIf your design requires a plugin to be readable, it's a bad design.
- jrockway 7y agoSo you want websites to override your decision on window sizing and make the visible area smaller? That doesn't sound great to me.
- iso-8859-1 7y agoIt's common practise. It's how web pages commonly work for the last 15 years. Do you prefer Gopher over HTTP/HTML as well? I actually do. This page lives in some in-between universe where all users have their own client side style sheets but still use HTTP/HTML.
- zzo38computer 7y agoFor a lot of stuff, Gopher is much better than HTTP/HTML (not for all stuff; and there is also stuff where neither Gopher nor HTTP(S) is good). I also don't like the webpage stylesheet resizing it and ignoring window size; instead it should just use the window size, and the user should change the font, font size, text width, etc, if they want to do so (also, they should implement split-screen). That is why I use user CSS.