5 ms·
I'm gonna complain about HN though; while it may not have been intended to be mobile first, it kinda is, leading to overly wide text in comments if using a full
by Cthulhu_ 3y ago
I'm gonna complain about HN though; while it may not have been intended to be mobile first, it kinda is, leading to overly wide text in comments if using a full screen browser. This is the same issue that the previous iteration of Wikipedia's design had.
- ryandrake 3y agoAs a user, when I set my browser to be full screen, I expect the content to take up the full screen. I bought a nice big 27" monitor, and I want to use it. How dare some UX designer 2,000 miles away from me simply decide that I should only be able to see content on a 5" wide strip down the middle! The browser should be the User's Agent, not the Web Developer's Agent. If I want to do something with my browser layout that a designer finds appalling, that should not be his concern. If the web developer and designer really think that text should appear in tiny 5" columns no matter how wide my browser is, fine, then flow your design to display multiple side-by-side columns like a newspaper. Don't just fill my screen with whitespace.
- bee_rider 3y agoI think multiple side-by-side columns would be great. Actually, do you know of any sites that actually re-flow text like that? It’d love to see it. I don’t really want text to reflow to be, like 23, inches wide or whatever. Books with 23 inch wide pages are quite rare, because, I think, that is too much horizontal space, scanning that far with you eyes can become a drag. Of course, if a page just uses the whole width uninterrupted for text I can just give it half the screen, so that is fine. But I’m curious, do you actually like the look of a page like that? Or is this just on principle—respect user choice and all that (if so, good principle!) In general web devs seem to think way too much about the layout of pages, if they would just do the simple thing users could resize the window to their liking.
- ryandrake 3y agoI think I might have seen the "column-ization" method once and was impressed by it. HN's handling of different browser widths is... pretty weird, at least on my Desktop Safari browser. Looks like from browser widths of 1920px and greater, HN maintains fixed size whitespace borders and scales the content width. Nice. When you shrink the window past 1600px, it holds the content size fixed and shrinks the borders. I guess the intent is to smoothly transition into a mobile design without the borders. Past 1516px, it removes the borders altogether, and seems to transition into this "mobile" design. Between there and around 610px, it seems to shrink the content width by discrete fixed amounts every 200px or so, to "keep up" with the browser width. Finally, below 610px or so, the site goes back to the non-mobile design, laying out as if the browser was 1600px wide (and actually truncating the right hand side of the text)--totally broken. All that complexity--for a text only site! When they could just make the text 100% of the browser width and let me as the user decide what is comfortable to view. It's still much, much better than sites that just limit the content width to 600 pixels and fill everything else with whitespace!
- SAI_Peregrinus 3y agoMulti-column layouts only work if there's no vertical scrolling, or at least if the layout reflows so that there's no need to keep scrolling down & up & down to read each page of content.
- carlosjobim 3y agoPagination is much better than stupid scrolling, that's why we switched from scrolling to pages a thousand years ago.
- SAI_Peregrinus 3y agoIf it's done well, pagination is nice. But (as in my previous post) I'm reminded of PDFs of multi-column articles where the text is tiny and doesn't re-flow when zoomed so you end up zooming in on the page to be able to read it, then scrolling down to read the text that's now off the bottom of the screen, then up & over to the next column, down towards the bottom again, etc. Then finally down to the next page & back across to the first column. That is a much worse experience than just scrolling in a single direction. It's fixable, of course, by "just" re-flowing the text to match the viewport size. On a desktop, pages of multi-column text at a readable font size are nice. On a phone, multi-column text would be annoying, but a smaller font size can be used because phones are typically held closer to the face than computer monitors. Getting the layout to work correctly like this isn't something I can actually remember ever seeing, but it'd provide a "best of both worlds" way of reading.
- carlosjobim 3y agoColumns that adapt to window height is a solved problem, if you for example check out epub.js [0] or the built in ebook reader in Yandex browser. I'd say this is a "just" problem with no particular difficulties to implement. Continuing with scrolling as default instead of pagination after the switch to high-res wide screen monitors was a mistake by browser makers. The future of the web - I think - will be with browsers that are real user agents and open every web page in reader mode, with multi-media presented exactly as the user wants. No more letting web-sites control CSS. As for web-apps, they are not the web, they are programs and should live as PWAs in the OS instead of as bookmarks in the browser. Like you wrote, there is little reason for column view on phones. Their width is one column and no more. I agree with you that it's strange that we never see this, especially on blogs or newspaper websites, where column view should be used. [0] https://futurepress.github.io/epubjs-reader/ https://futurepress.github.io/epubjs-reader/
- cal85 3y agoYou suggest that a site owner should design the page how you want it, not how they want it. But neither is the case. Their task is to design it in a way that is acceptable for many different people. For most users, maximising the browser window does not mean they want text paragraphs to become very wide, it just means they want to block out distractions. And most readers benefit from plenty of whitespace and a conventional line width of 50-70 characters. It’s not that the designer is appalled by your preferences, it’s just that you aren’t the only person who matters. You say the browser “should” be your agent - but it is. You can use ‘reader’ mode or any number of browser extensions to tailor things for your own tastes, or even copy and paste the article text somewhere else to read it however you want. What you cannot reasonably expect is for every site to be ideal for your personal tastes out of the box.
- ryandrake 3y agoI guess I just expect the web site to at least not deliberately make itself terrible such that users have to resort to big hammers like extensions, "Disable Styles", "Disable JavaScript" and "Reader Mode". Web sites are fast, flexible, responsive, readable, scrollable, accessible, and respectful of user preferences... by default, from the moment you add text between <body> tags. Then web developers add code and CSS to make them worse. Sometimes they make it better, but very often it's worse.
- cal85 3y agoIt sounds like you prefer that 'academic' style that rests heavily on browser defaults. I personally like that style too, it's not an uncommon preference for HN users. But you must realise it's very niche? Most users of most websites find that kind of design difficult to read and use, so it's rare to see it outside of academic/engineering circles. All you're doing here is asserting your own niche preference, and making out that it's what the majority of people want. It isn't. That's why designers design things the way they do, not (in general) because they are incompetent or malicious. And that's why it's great that you have the option of using extensions/reader-mode/copy-pasting/whatever, so you can effectively redesign anything just for you with a small amount of effort. If you expect everything to already be designed for your own unconventional preferences, at the expense of most other users, then that is unreasonable.
- lopis 3y agoVery wide paragraphs is just bad accessibility. It's harder to read and there are studies on this. You can always just disable the page styles if you hate it.
- danShumway 3y ago> As a user, when I set my browser to be full screen, I expect the content to take up the full screen. I bought a nice big 27" monitor, and I want to use it. How dare some UX designer 2,000 miles away from me simply decide that I should only be able to see content on a 5" wide strip down the middle! I've seen this argument come up before multiple times on HN, and it's wild to me. Having sensible CSS defaults is not a designer dictating that you are only able to see content one way. You might prefer to read text in a giant line spread across a giant monitor, and that's fine, but it's not a freedom thing. It's not denying your browser's role as a user agent that sites have CSS files. Every single website (HN included) makes CSS decisions for the user. What colors should be used, what is the default contrast. Every single line of CSS on a website is a designer decision by a designer 2000 miles away from you about how they think that content should be presented. And if you don't like that, turn off CSS in your web browser. Assuming you're using Firefox (which you should be using), it's trivial to do. Of course, browsers should allow overriding CSS, and (imo) they should make it easier to do so and more accessible to non-technical users. And yes, part of making a website that respects the browser as a user agent is shipping HTML that can be viewed unstyled and that is easy to override styles for. Ironically, HN does a horrible job of this -- the HTML is not semantic, the use of tables is so egregious that even stripping the CSS out doesn't really remove all of the styling. The site is really messy if you want to override anything. So that HN uses a design that happens to more closely align with what you want does not make the site more respectful of your browser as a user agent. It just means that you and the designer(s) happen to like the same design. And in comparison, putting `max-width: 45em` on a text column is not even remotely user hostile, it is a very simple CSS property to override -- especially for designs that use single columns because you can change that CSS property without even worrying about reflow. `max-width` is a default that statistically works better for the majority of users even on large monitors (I use a 32 inch 4K monitor and max-widths make text on that monitor easier to read). But of course, some people are different, and that's fine. Go yell at the browser makers to allow easier CSS overrides, or turn off CSS entirely, or install an extension that lets you add CSS to given pages or spend a weekend building an extension that strips max-width out of stylesheets for every website you visit, or customize Firefox's userContent.css file. There are options here. And if you had made an argument about those options, I'd be 100% on board. CSS for websites should be treated as a default setting instead of as a requirement and browsers should support CSS overrides more easily out-of-the-box. But the idea that designers are denying user agency by not making a proactive design decision to present by default the specific format you want to read -- it's just ludicrous. You're not asking for user freedom, you're asking for designers to target your preferences instead of other people's. Those two things are not the same.
- stronglikedan 3y ago> overly wide text That is completely subjective though, and the user has the option to not use a full screen browser to view the comments. I personally prefer it.
- agos 3y agonot completely: line length for readability has been subject of interest for centuries
- carlosjobim 3y agoYou have the option to make the window more narrow, this is not a fault of the designers.
- denton-scratch 3y agoDisagree; I don't want to have to resize the window each time I switch browser tabs. Sites should work independent of the amount of real-estate my browser is taking up.
- carlosjobim 3y agoThen pray for adjustable margins to come to the web browser like in Wordpad three decades ago. That would actually be quite nice.
- gwbas1c 3y agoMaybe "Refined Hacker News" should fix this. See: https://github.com/plibither8/refined-hacker-news https://github.com/plibither8/refined-hacker-news Edit: You can use the F12 debugging pane to adjust the width of a single tab without resizing the window. It's kind-of a hack, though. Just push F12 and drag.
- arboles 3y agonews.ycombinator.com###hnmain:style(max-width:100ch) Paste this line to uBlock Origin My filters
- euazOn 3y agoThanks. You have ever so slightly improved my life. I should've done this earlier.
- deleted 3y ago[deleted]
- aimor 3y agoWell, I tried setting `resize = "both"` on everything, but it was a bit of a letdown. It would be a neat experiment to have every element of every webpage be interactable (let's say resizable by dragging edges, and modify colors from the right-click menu) with edits persisting between visits. Array.from(document.querySelectorAll('*')).forEach(el => {el.style.resize='both'})
- gwbas1c 3y agoPersonally, I find HN difficult and frustrating on mobile: It's all tiny text. Then again, I rarely read HN on mobile. It's just not the kind of stuff I enjoy looking at when I'm "on the go." Perhaps that's why they never tweaked the layout for mobile? > ...leading to overly wide text in comments if using a full screen browser. IMO, that's a bug, both with HN, and with the "default" styling in a browser.