1. 14
  1.  

  2. 5

    I’m not against change but I am getting furious every time I end up in the mobile page because I do switch between different language articles ALL THE TIME and that’s the one feature from the sidebar that is completely hidden on mobile. I seriously hope they won’t hide that…

    1. 4

      You mean switching between languages for a specific article? I have that button under the article title on mobile. What I can’t find is a link to the article’s talk page, which on some niche articles contains as much useful info as the main entry.

      1. 3

        The talk page is, at times and in places, the only redeeming feature of wikipedia. Ok, that and the edit history page. Of course they wouldn’t want to expose those to the great unwashed masses of mobile users.

      2. 4

        As danburzo said, there is this button under “articles” with an japanese sign and an stylized ‘A’. I didn’t know before an japanese speaking friend shows me. I to used to request desktop version even on mobile. But not after that. I think that function is to obscure and hidden.

        1. 1

          Hehe, thanks all! No, I didn’t notice that one, but I absolutely checked the bottom of the page several times…

          1. 1

            Also took me way too long to realize this random button is hiding the menu I was searching for all the time.

        2. 1

          I use the mobile app for that. You can even search in multiple languages at the same time.

          Btw I am still mad that they removed the geolocation feature to discover cool things around you from the app.

        3. 4

          One thing I’ve found amusing is that Vector (the current default MediaWiki skin) isn’t responsive, whereas MonoBook (the old default MediaWiki skin) has been updated for responsive design. It actually feels pretty good on mobile - and should probably be applied to Vector, because as a desktop user, getting mobile Wikipedia links is incredibly annoying.

          1. 3

            I wrote a minimal typographical rehash of wikipedia a while back to fix the annoying line width issue, though it probably does a little more than that.

            It’s great to see wikipedia is finally trying to fix this issue, but from my inspection, the new layout seems to assume a fixed screen width. If the screen is too narrow or if the page is zoomed in, it enforces horizontal overflow instead of shrinking the text width. Compare the old layout and the new layout at 200% zoom level on a 16:9 screen.

            This particular design decision can be problematic. The new design is no longer responsive and forces the user to view the page at default font size, which is too small in my opinion. I used to be using browser’s zoom feature on desktop to compensate for the long text width, but this update will be likely to break this trick.

            1. 1

              The layout on fr.wikipedia.org is pure crap. I’m trying to remain calm by and not assume that they haven’t tested it but instead that they haven’t tested enough configurations.

              Screenshot: http://notk.org/~adrien/wp_fr_design_crap.png

              The broken layout is difficult to describe. I think the closest fuck-up is “IE6 on the ACID 2 test”.

              1. 1

                And I just found out about wikimili which brands itself as “the best wikipedia reader” and it doesn’t have visible trackers, plus it loads really fast. Example page: https://wikimili.com/en/Non-return-to-zero (what made see that page was a discussion about whether HDMI had moved beyond NRZ modulation or not; it seems it hasn’t).

            2. 3

              I’m very excited about the addition of a maximum line width rule. I’ve been moaning about it for years, and it is the only reason I have Stylus installed on Firefox.

              I’m glad that they have justifications for the changes that consider the users - the article started off sounding like it was change for the sake of change. After that it was some of the most thoughtful thoughts on design that I’ve seem in a mainstream project for a while.

              1. 2

                The maximum line width rule is something I hope I can easily override with custom CSS. It makes websites more difficult to read, a single column of text lost in whitespace, you eye unable to see sentences because they’ve been chopped up and sacrificed on the altar of usability.

                1. 2

                  I wasn’t expecting anything more complex to be done than something like max-width: 80ch; which should be easy enough to override. Having said that, some of the other comments suggest it might not be so simple.

                  I’ve never heard anyone before say that they prefer screen-width lines so I’d love for you to elaborate on that. Is this something that bothers you in other mediums, say magazines or posters, or purely on computers? What is it about sentences being written across multiple lines that you dislike, and is that not also a problem in books, or indeed Wikipedia? Sentences often crossed line boundaries, but for me it was the longer lines that made it harder for me to find the start of the next one.

              2. 2

                i’m going to hate this but it’s not worth trying to do anything about it. who wants to bet that the new design will have a sticky nav bar that occupies an inch of our already too short laptop screens?

                i suppose i can start logging in to wikipedia, and select a classic skin. but it will be a drag to have to maintain logins and be annoyed when using another computer.