On Monday morning we (Mozilla) detected a very large crash spike affecting #Firefox users on Linux, specifically on an older version of a Debian-based distribution. It turned out to be an interesting bug involving the #Linux kernel and #Google JavaScript code so let me tell you about it. A thread 🧵

  • Spectacle8011@lemmy.comfysnug.space
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    It is interesting though that we find ourselves working around a bug we did not introduce triggered by code we do not control.

    I imagine a lot of a browser’s codebase looks like this. From what I understand, browsers expect webmasters to screw up their markup and make allowances for it.

    • monobot@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      I love Firefox and understand that making modern web browser is monumentally complex, but browser should not crash what ever some website does.

      That said, my Fennec is having problem with googlw images.

      • Spectacle8011@lemmy.comfysnug.space
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        but browser should not crash what ever some website does.

        Sometimes crashing would be better than trying to beat wonky code into shape: https://samy.pl/myspace/tech.html

        1. Sweet! Now we can do javascript with single quotes. However, myspace strips out the word “javascript” from ANYWHERE. To get around this, some browsers will actually interpret “java\nscript” as “javascript” (that’s java<NEWLINE>script). Example: <div id=“mycode” expr=“alert(‘hah!’)” style=“background:url(‘java script:eval(document.all.mycode.expr)’)”>

        But on principle I agree. I can’t say whether Google Images works or not on my Firefox browser, because I’m using Mojeek.