This December, if there's one tech New Year's resolution I'd encourage you to have, it's switching to the only remaining ethical web browser, Firefox. According to recent posts on social media, Firefox's market share is slipping. We should not let that happen. There are two main reasons why switchin
  • DirtyCNC@lemmynsfw.comEnglish
    4·
    1 year ago

    If you’re reading this and not using Firefox, do yourself a favor and don’t wait until 2024 to switch.

    • platypus_plumba@lemmy.worldEnglish
      1·
      1 year ago

      I’ve had many problems with Firefox that always push me back to Chrome. It seems some web pages are only created with Chrome in mind. I really don’t know about browser specs but I’m guessing a front-end app must have a lot of “if chrome, then; else if Mozilla then;” logic to handle specific browser interfaces or features.

      Apparently some apps don’t care about Mozilla and they just don’t work. It’s also pretty hard to tell that the issue is Mozilla, it takes me like 15m to switch to chrome and then “ahhhh… it was the browser”.

      I really want to help Mozilla by using it, but I just can’t under those conditions.

      • fifisaac@lemmy.worldEnglish
        4·
        1 year ago

        What sites are these? I’ve not had this in years and when there is problems the site normally says unsupported browser rather than leaving me to guess

        • DirtyCNC@lemmynsfw.comEnglish
          1·
          1 year ago

          Other than YouTube, which purposefully slows Firefox down, I only ever encountered one webpage in years where the issue was 100% “caused” by my browser choice – the left pane (lesson list) in my school’s tutoring platform would not scroll due to what I assume was a trivial HTML oversight. After reporting the issue, they insisted that they would not support browsers other than ones based on Chromium and Safari and tried to convince me to switch. I don’t have access to the site anymore and I did not understand web development at all back then so I could not create a patch myself; I just worked around the issue using a very tall, zoomed-out “mobile view” to reach the off-screen buttons.