I want to start by saying that WS has nothing to do with the code. The code is provided "somewhere" up the line from an ad vendor. This code is not what is provided by any of our ad vendors for us to use, but is inserted from a call made by whichever vendor. Again WS does not include that code or any of the final ad code.
Why is that closing script tag different from what you are used to? Very simple it is a nested script tag and therefore cannot be handled the same way.
To learn more about nested javascript, here is a google search
https://www.google.com/search?q=</s...22&ie=UTF-8#q=nested+script+tag+in+javascript
Turning off javascript is not a solution but instead creates more issues. I can offer no assistance to anybody who follows that advice. Instead, I suggest following the instructions at
http://www.websleuths.com/forums/sh...ion-Information-to-fix-problems-on-Websleuths This will allow me to track down and eliminate saymedia from being able to advertise.
Finally to clear the other misconceptions, Blocking saymedia will in fact solve the problem(for those where saymedia is the problem). If the code is blocked from ever being placed on any of our pages, why would a browser try to render what you thought was broken code?
This has absolutely nothing to do with "
servers are dealing with excess data usage".
I have blocked 1 ad supplier form showing anything saymedia, with the proper information as outlined above I can block another. Yet another may still be serving saymedia, we can again get the proper code for this vendor. At this point there are 3 vendors, 1 blocked, and I will be waiting for you to give me the info on the second. After that we will see what is going on with the 3rd, but they have already told me that though they have a business relationship with saymedia, they do not show ads for them.
All the above said,
1- the code could have been written better, nothing I can do about that, but it is not what I would consider broken. It is proper for most(99.something%) user-agents. But 1 more split script and an escape could have made it 100%.
2- I am unable to help anybody who turns off javascript as any problems a user will encounter will probably be self imposed.
3- I do NOT expect blocking saymedia to solve the problem for most users who are facing it. It very well may for a percentage though.