Collapsing AdSense versus Norton Firewall

A minor, minor point

[Wail]

Like everyone else, I spent last night playing around with the new features. The Collapsing AdSense feature made a lot of sense for, a lot of, er, ad sense.

I downloaded the collapsing half of the script, opened it up and was surprised to see a symError() JavaScript function in it.

What the hec... ah, it's Norton again. Norton Firewall webmaster users will be well aware of the symError() insert into source code. I was totally unaware that it placed it in downloaded .html content though.

I removed it.

What are the chances of both Google and Symantec having a padder symError() function? Slim to none; so I'm sure I did the right thing by removing it. Right?

It leads onto ponders about modifying the collapsing code. Without even checking the T&Cs I'm sure we're not allowed to. It's a bugger. If I want adverts in my side bar then they'll need to be part of a div tag set (for the sidebar decoration). If the adverts aren't going to be there then I don't want an empty div tag space as it leaves a trace of effects (borders, a sliver of background colour, etc). It makes sense to put the div tag inside the collapsing code insert.

Anyway, the subject of this post was Collapsing AdSense versus Norton Firewall and the point is: Caution Norton users. Don't unwillingly insert useless and T&C breaking Google code into your site.

[Bluepixel]

The collapsing adsense feature is not a well thought.
The adsense script shouldn't define any size if no ads are shown, so the user could with his alternate ad decide how big that area should be.