We’ve been anticipating it for years,1 and it’s finally happening. Google is finally killing uBlock Origin – with a note on their web store stating that the …

  • beastlykings@sh.itjust.works
    link
    fedilink
    English
    arrow-up
    0
    ·
    30 days ago

    I recently switched back to Firefox, and almost immediately ran into an issue where I couldn’t log into Dropbox. It took me far longer than I’d like to admit, to realize that Firefox as the problem. I popped into edge and logged in immediately no problem.

    I’m still gonna will with Firefox, but it’s annoying that it doesn’t work all the time.

    • yoasif@fedia.ioOP
      link
      fedilink
      arrow-up
      0
      ·
      30 days ago

      Uhh, that doesn’t seem normal at all. Is this a default config? Any extensions in use?

      • beastlykings@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        0
        ·
        29 days ago

        Fresh install of Windows 10, fresh install of Firefox, fresh install of Dropbox.

        I was trying to log into Dropbox to authenticate the app, but every time I got to the part where I had to enter my 2fa it would say it was expired. I grew concerned that I was hacked and it was changed, but trying it on my old computer it worked fine.

        Then I said fine, I had accidentally paired my Dropbox account with my Google account years ago, so I guess I’ll use that. So I logged into Google, and then clicked sign in with my Google account, and I got stuck in a loop where the page was refreshing everything few seconds.

        The page would load, it would say “signing you in with your Google account”, then it would say at the top in red letters something like “sorry, you haven’t signed in recently enough to do that, please log in”, and the entire page would refresh and start the loop over, “signing you in with your Google account” etc etc. I left it go through several cycles, it was never gonna work.

        It was about then that I guessed that Firefox might be the problem, and it was 🤷‍♂️

        The only non standard thing about my config, is that Windows is inside of a VM. That could very well be it too? But edge was also in that same VM, and it worked. I only used edge because I’m trying to keep the VM light, so I didn’t install chrome for a one off thing.

        I don’t know why I got down voted in my earlier comment, I’m not pooping on Firefox. I honestly want it to work, and am still going to use it. But the facts are facts, I literally just ran into this issue yesterday 🤷‍♂️

    • Natanox@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      0
      ·
      29 days ago

      This is part of Googles strategy. Ever since the Chromium engine took off enough and everyone else fell behind they began introducing more and more changes that merely benefits them, with less public debate or proper communication (or even adherence to common standards). Last thing I remember, aside of manifest v3, was them killing off JPEG XL as it was a competitor to webp and webm (which they control). JPEG XL was actively worked on and would’ve probably turned out better before they killed it without any previous notice.

      Given Googles dominant market position, their influence and everyone wanting to cut corners wherever possible sometimes Firefox support is just ignored.

      tl;dr It’s not Firefox’ fault. It’s Google’s sabotage.

      • beastlykings@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        0
        ·
        29 days ago

        Ah I see, it sounds like I’m saying it’s Firefox fault. No I definitely agree, chromium is the largest market share, and gets the most support, and doesn’t always follow standards, so some websites will have compatibility issues if they don’t specifically focus on Firefox support.

        It’s just a sucky situation.