71–80 of 288 posts
Gut reaction: I hate it. But I'll probably get used to it...
Yeah, same reaction for me... I've always liked the small gradients on the top and the long list of things down the left side which I never click. Felt homely. I'll miss it.
I sense part of what drove this redesign is the fact that 4K and Ultrawide monitors are now common enough that designing to accommodate them cannot be ignored. That being said, I much prefer left-justification instead of centering the content and having massive whitespace islands to either side. I wish there was an option to left justify.
My personal problem with it: the sidebar became wider. Now I have to disable it, but when I disable it, it disappears and makes the text lines much wider than what I'm used to. I'm one of those few people who don't maximize the browser to get a good acceptable line width. Wikipedia simply broke this :(
I browse with Safari on iOS with JS disabled by default. I do this for privacy and accessibility reasons (gotta stop those annoying popup modals, trackers and other annoyances). One thing I noticed with Wikipedia with JS /enabled/, all the sub-categories of a topic are by default, closed. But when I browse with JS disabled, all the sub-categories are /opened/ and I have the full article . Since most people browse wit…
Is this actually true? I'm curious if anybody has sources for this and if it's a common UX practice. I tend to use wider windows than traditional 8:9 half-screens and this max-width practice drives me nuts.
(sorry)
Is there a way to change it back?
My initial take: I actually like this a lot. The body text is narrower which makes for easier reading. The sidebar with an updating highlight of current place in document is really nice too. I don't mind the "wasted space": Wikipedia is primarily about reading, and any well typeset book or web page should have generous margins so the line length is not too long.
Text width is important, but this is not a solution, zooming and changing browser window geometry is.
I don't need a header to follow me down the page, in fact I'd prefer it not to. On the very rare occasion when I need to scroll all the way to the top of the page, I have no problem figuring out how to do that. Feels like they're introducing a persistent UI element without a benefit. Benefit to me, anyway. Maybe they heard from a lot of users who were having trouble remembering where the header was, I can't say. I do…
I don't need a header to follow me down the page, in fact I'd prefer it not to. On the very rare occasion when I need to scroll all the way to the top of the page, I have no problem figuring out how to do that. Feels like they're introducing a persistent UI element without a benefit. Benefit to me, anyway. Maybe they heard from a lot of users who were having trouble remembering where the header was, I can't say. I do…