Rikudou_Sage@lemmings.world to Programming@programming.dev · 24 days agoI always feel better about myself when I see huge companies pull off shit like thislemmings.worldexternal-linkmessage-square22fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1external-linkI always feel better about myself when I see huge companies pull off shit like thislemmings.worldRikudou_Sage@lemmings.world to Programming@programming.dev · 24 days agomessage-square22fedilink
minus-squarefinitebanjo@lemmy.worldlinkfedilinkarrow-up0·24 days agoI was getting that the other day on a random site on desktop, maybe it’s got something to do with firefox/waterfox?
minus-squarebrbposting@sh.itjust.workslinkfedilinkEnglisharrow-up0·24 days agoCan adblock “cause” it?
minus-squareDannyBoy@sh.itjust.workslinkfedilinkEnglisharrow-up0·23 days agoI don’t think so. This is the code crashing, Adblock just blocks requests.
minus-squareBlackEco@lemmy.blackeco.comlinkfedilinkarrow-up0·23 days agoNot directly, but if the developers would call some global variable set by a third-party library that’s blocked by an ad-blocker (say GTM) without checking if said variable is set first, that probably could trigger that error.
I was getting that the other day on a random site on desktop, maybe it’s got something to do with firefox/waterfox?
Nah, it’s a Next.js error.
Can adblock “cause” it?
I don’t think so. This is the code crashing, Adblock just blocks requests.
Not directly, but if the developers would call some global variable set by a third-party library that’s blocked by an ad-blocker (say GTM) without checking if said variable is set first, that probably could trigger that error.