2 ms·
When I read to the end I found that author proposes a mechanism that is far less convoluted than google's and devoid of this similar problems. It's better to h
by DenisM 18y ago
When I read to the end I found that author proposes a mechanism that is far less convoluted than google's and devoid of this similar problems.
It's better to have less code in your page and more code in google's script - that way they can patch it without me getting involved. As it is now they added the try/catch block (really helps if users run ad-block or some such) but most web admins have not updated their stuff.
- eli 18y agoThough he accomplished it by altering the requirements. His solution does not work seamlessly with HTTPS sites -- it requires a server-side changes to the code. That's a pretty big issue for a script that's supposed to "just work."
- DenisM 18y agoBut it doesn't "just work" - it breaks it the face of some firewalls and pops an exception if user has adblock. I actually had users complaining about the latter, this is not a theoretical problem (I fixed it with try/catch myself, but it should not have been a problem to start with and demonstrates brittleness of google analytics). In other words it's a tradeoff between http/https transparency and odd errors on user's end. Pick your poison. :-)