Errors

[Petie]

not to preach or anything, but isn't it up to the site developer to follow standards?
because who doesn't use content blockers now-a-days, it's kindof a standard in itself.

I just want to point out that I do follow standards. Every page that I've written is HTML5 and CSS3 compliant and those are actual standards. What you're implying is that I should have to write sloppy code to account for the fact that extensions might screw up my site, which is kind of an absurd notion. How do I know who's using what? I can't really plan for everything. As a result, I've always taken the approach that I will code the site correctly and if it breaks for people who are disabling our ads or otherwise modifying our site content in transit, then so be it. I don't intend to waste my time coding in workarounds for people who aren't even doing the bare minimum to support the site.

Now, don't get me wrong. I do get where you're coming from. We do our best to keep malicious ads out of our rotation but the system isn't perfect and occasionally, something gets through that shouldn't. That's the nature of the game and it's here to stay unfortunately. The only other thing we run is Google Analytics which is harmless, essentially. Does Google have some way of connecting the anonymous data you leave behind here to the anonymous data you leave behind elsewhere? Probably. But you can't really expect absolutely privacy online ever.

All that being said, if you're careful, it's difficult for an ad to infect you. You still have to willingly interact with it in some way unless you're running something like an old XP install that's never been patched. So I do think the approach you're taking is a bit overkill but I still don't fault you for it. You're welcome to block or not block whatever you want but we're also welcome to ignore error reports caused by third party modifications.

I apologize if this comes off in an angry tone. I'm not angry. I wound up responding to a rant with another rant which really wasn't my intention but it does adequately address the issue so I'll leave it. If you have any questions or concerns, don't hesitate to ask. As for your error, just follow through with determining which extension is causing the problem and you should be good to go, at least in terms of figuring out what you have to do to fix it.