191–200 of 288 posts
Not that it matters to most people, but I'm surprised this didn't break the Dictionary app on my 10-year-old version of OS X (10.9 Mavericks). Wikipedia inside the Dictionary app looks basically identical to how it did a week ago, even though aiui it's basically just rendering the Wikipedia page (in a now terribly outdated browser engine) with some custom CSS. I wonder why it's still working.
Earlier quoted context omitted.
You can fix these errors if you want to. Anyone can edit Wikipedia.
How would I fix the errors? I know Wikipedia is lying to me. I can delete the information, which is pretty likely to get reverted. But I can't replace it with correct information; I have no idea when the idea of bread fried in eggs is first documented, and I have no idea whether or not the stock character of Chen Shimei is based on a historical person. For all I know Wikipedia is lying about the publication date of t…
Earlier quoted context omitted.
Interesting. I'm curious if you're seeing this on desktops? My sample of mac users is very heavily biased towards laptops (and I've only used macos on a laptop) - but I've seen the exact opposite.
Desktops and laptops. I do see more Mac users with maximized and/or full screen windows on particularly small laptops. (And I'll note that in my own usage, when I'm on my 11" Macbook Air I full screen most apps. But that's a weird edge case due to the screen size.)
Earlier quoted context omitted.
The article addresses this by mentioning that they referenced research demonstrating text that is too wide causes people to read less comfortably and retain less information. The page gets much less padded when you reduce the size of the window, because the padding isn't there to make blank space, it's there to enforce a maximum line width.
> text that is too wide causes people to read less comfortably and retain less information. This seems like an excuse to force JS to enable ads & what should be the default that is toggled with the fullscreen button in the bottom right. It does not justify wasted width as the user can more easily set the text to the appropriate zoom than applying some custom CSS: .mw-page-container { max-width: none !important; } .mw…
No, it's an accurate description of most users' reading preferences, myself included.
Earlier quoted context omitted.
Text width is important, but this is not a solution, zooming and changing browser window geometry is.
I think if you really want full-width text, you could write a little custom CSS to make it work how you want it. As it stands, I think the new design is a much better default for most people. Also, zooming and changing browser window size is, while only a keystroke away, isn’t something I want to do just to make a site that should be optimized for reading text more legible. It should just default to that way. In shor…
How? Seriously, if you have a way to do this that works for pages in general I'll be extremely grateful. I tried using a user stylesheet that said * { max-width: 100% !important } for a while, but that breaks too many non-root elements on all sorts of sites.
Whereas making the page narrow when it doesn't set a max-width seems very easy to do with a custom stylesheet.
Earlier quoted context omitted.
I guess it depends on the person. I'm happy to accept that I'm strange, but I'd much rather read lines that mostly fill my screen with normal margins on each side than short lines in a long narrow column surrounded by an ocean of empty whitespace. I can't be the only one who feels this way. I have yet to buy a book where 90% of each page is blank and there's just a tiny column of words down the middle of the page.
I don't normally read books that are anywhere near as large as a 27" monitor, and when I do they often have pretty massive margins (or "whitespace"). I mean seriously, a 27" diagonal monitor is 24"x17". Do you routinely read on 12"x17" paper with near zero margin?
Earlier quoted context omitted.
The article addresses this by mentioning that they referenced research demonstrating text that is too wide causes people to read less comfortably and retain less information. The page gets much less padded when you reduce the size of the window, because the padding isn't there to make blank space, it's there to enforce a maximum line width.
> text that is too wide causes people to read less comfortably and retain less information. This seems like an excuse to force JS to enable ads & what should be the default that is toggled with the fullscreen button in the bottom right. It does not justify wasted width as the user can more easily set the text to the appropriate zoom than applying some custom CSS: .mw-page-container { max-width: none !important; } .mw…
Do you realize the level of entitlement and absurdity here?
Earlier quoted context omitted.
I think if you really want full-width text, you could write a little custom CSS to make it work how you want it. As it stands, I think the new design is a much better default for most people. Also, zooming and changing browser window size is, while only a keystroke away, isn’t something I want to do just to make a site that should be optimized for reading text more legible. It should just default to that way. In shor…
> I think if you really want full-width text, you could write a little custom CSS to make it work how you want it. How? Seriously, if you have a way to do this that works for pages in general I'll be extremely grateful. I tried using a user stylesheet that said * { max-width: 100% !important } for a while, but that breaks too many non-root elements on all sorts of sites. Whereas making the page narrow when it doesn't…
My point: if you care that deeply about how Wikipedia in particular is laid out, you likely have the tools to force it to work that way. Meanwhile, the rest of us plebs get a better (from a typographical standpoint, not necessarily a case-by-case basis) default.
Earlier quoted context omitted.
Why not just have multiple columns of text instead of half a screen of emptyness and stuff users rarely interact with? You could arrange the different wiki sections to be side by side.. in a dynamic responsive way depending on device/screen size
I find multicolumn on digital screens especially in the browser to seem very clunky. And with an arbitrary article length, multicol would require pagination, right?
I see some examples on MDN:
https://developer.mozilla.org/en-US/docs/Learn/CSS/CSS_layou...
I imagine there are a few ways to do it. I'd just have columns break at section headers. It'd also jive well with the wiki pic/quick-info right hand sidebar that's common