Google has rolled back a recent release of its reCaptcha captcha script after a bug caused the service to no longer work on Firefox for Windows.
    • TheTetrapod@lemmy.world
      20·
      6 months ago

      I mean, the fact they rolled it back and didn’t just add an error message telling you to use Chrome is a little surprising.

  • dhtseany@lemmy.ml
    55·
    6 months ago

    God forbid they tested across the multiple common browsers out there other than Chrome. Every other software development company creating a web app does that, why doesn’t one of the biggest?

    • dragnet@lemmy.dbzer0.com
      343·
      6 months ago

      Sadly no, ever web app company definitely doesn’t test under Firefox. I’m at the point where I use Firefox for general web browsing and Chromium for most web apps.

      • ripcord@lemmy.world
        7·
        6 months ago

        In the last 5 years I’ve run across maybe 1 site that didn’t work properly in Firefox. And another that MIGHT not have worked right, but I was only guessing it was related to FF.

        However, since FF dropped PWA support I do use Chrome for a handful of sites that either are PWAs or you can use Chrome’s open as application feature, which is real nice for a few things. Is that what you mean by “Web Apps”?

        • dragnet@lemmy.dbzer0.com
          1·
          6 months ago

          No, the PWA thing is a separate annoyance. What I find is that in a lot of web apps, the app mostly works fine but has bugs that break certain things or are seriously inconvenient in Firefox only. Two I’ve experienced recently are Nextcloud Office slideshows (I need to search for/open a bug report honestly) and a web based billing software we use at work.

          • ripcord@lemmy.world
            2·
            6 months ago

            Thanks. I remember trying it about a year ago but it didn’t work well for some reason. Will give it another try now that I hear it’s working well for you.

    • JackGreenEarth@lemm.eeEnglish
      4·
      6 months ago

      Me too. But I mainly code for myself, nothing mainstream, so it doesn’t usually matter if it works on other browsers. Usually it does anyway, though.

    • sugar_in_your_tea@sh.itjust.works
      1·
      6 months ago

      Same, except I’ve been using whatever Tauri packages lately, which on Linux seems to be a webkit browser.

      We support only Chrome at work (B2B app), but I mostly use Firefox.

    • Legend@lemmy.sdf.org
      110·
      6 months ago

      c/foundthedevil ?

      Edit: These lemmings i swear look at the users name i replied to i was just making a joke .

  • elxeno@lemm.ee
    14·
    6 months ago

    The script attempted to modify a div’s background color using document.body.removeChild, but as the script was loaded in the HTML head, the DOM had not loaded

    Isn’t that how it works/always worked? When i was learning html/js ages ago i had to use some event listener (DOMContentLoaded i think) or put the script just before </body> (for any code that should run on load and interacts with the DOM).

    And how do you change the background by removing a child?

    • ReversalHatchery@beehaw.orgEnglish
      3·
      6 months ago

      And how do you change the background by removing a child?

      The removed child could also have a background color, and it could span the entire area of the parent element.
      But it’s weird because the quote says “modify a div’s background color”, and this way you don’t actually modify that, but only it’s appearance.

      Or maybe it’s done with some CSS trickery, looking for a specific child in it’s selector?

  • Black616Angel@discuss.tchncs.de
    6·
    6 months ago

    Wait, is that, why PayPal didn’t work and I nearly missed my train? Wow.

    And I thought the PayPal devs were stupid, but apparently it was google themselves.