• Evkob@lemmy.ca
    link
    fedilink
    arrow-up
    17
    ·
    11 months ago

    It renders a lot better on my phone, but this is why reader mode is a necessary feature for browsing the web on a smartphone.

      • Admiral Patrick@dubvee.org
        link
        fedilink
        English
        arrow-up
        11
        ·
        edit-2
        11 months ago

        That’s not responsive design’s fault. When done properly, it works great. Too many sites just implement it poorly and insist on the CVS receipt layout even on mobile (e.g. recursive CVS receipts). Gotta cram those margins full of ads, ya know?

        • ranandtoldthat@beehaw.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          11 months ago

          When done properly it is indeed a great practice.

          But so many don’t. The way the modern tech industry functions makes it hard to consistently get right, sadly. I’ve left two companies in the past two years where computational resources for automated testing and validation were simply not available. One didn’t have any manual QA beyond the implementing developer. I’m in a better situation now, but those companies still exist. They’re not exactly tiny startups either.

          For all its strengths, without any amount of validation, RWD is very likely to lead to such issues. Unfortunately many industry execs are unsympathetic, seeing RWD as little more than a way to get two things for the price of one.

        • TehPers@beehaw.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          edit-2
          11 months ago

          Looks like they’re using fat margins instead of max-width and nobody thought to use media queries to reduce them on mobile…

          Edit: I should add the page renders fine on my phone, FF android. I’m not sure what’s going on in the screenshot, maybe desktop view?