• ikidd@lemmy.world
    link
    fedilink
    English
    arrow-up
    137
    arrow-down
    2
    ·
    7 months ago

    So this is part of a larger adblock checker, if the ad doesn’t load within 5 seconds, it fails and triggers the adblocker warning. Since the ad should load in 3, they’ve set it for 5. If you have ubo, you won’t see the warning that it then wants to pop up, it just seems (and is) a 5 second delay. Changing the UA probably removes this from Firefox because then the clientside scripts will attempt to use builtin Chrome functions that wouldn’t need this hacky script to detect the adblock. Since they don’t exist, it just carries on.

    • localhost443@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      35
      arrow-down
      4
      ·
      7 months ago

      I was wondering how badly out of context the above quote must be considering the UA isn’t checked in the function. Above poster is trying to construe it as a pure and simple permanent delay for Firefox.

      That being said, the solution is still bullshit.

      • Adalast@lemmy.world
        link
        fedilink
        English
        arrow-up
        15
        arrow-down
        2
        ·
        7 months ago

        That is just the timeout function, not the call stack. It is likely called in a function that uses a UA check.

      • Cosmic Cleric@lemmy.world
        link
        fedilink
        English
        arrow-up
        11
        arrow-down
        5
        ·
        7 months ago

        I was wondering how badly out of context the above quote must be considering the UA isn’t checked in the function. Above poster is trying to construe it as a pure and simple permanent delay for Firefox.

        The UA check can happen before the function is called though.