Alex, do some basic input sanitization, mkay?
-
This greeted me today on the front page...
[img]http://i762.photobucket.com/albums/xx261/mehwhatever/wtfwtf1.png[/img]
.
.
.
[img]http://i762.photobucket.com/albums/xx261/mehwhatever/wtfwtf2.png[/img]
-
Input sanitisation is fine. It's just the routine that selects "the first bit of the article" to display it as a summary, apparently can't cope with the huge set of <param> tags that is used in the latest article to give the audio-blog preview. As a result, it cuts off half way through the containing DIV element, keeping the opening tag but not the closing tag. The rest of the document therefore falls into the unclosed DIV.
-
@TarquinWJ said:
Input sanitisation is fine. It's just the routine that selects "the first bit of the article" to display it as a summary, apparently can't cope with the huge set of <param> tags that is used in the latest article to give the audio-blog preview. As a result, it cuts off half way through the containing DIV element, keeping the opening tag but not the closing tag. The rest of the document therefore falls into the unclosed DIV.
It looks fine to me. Maybe you guys should get a real browser.
-
Unfortunately, RealBrowser doesn't work* on anything more modern than Win98.
*well, if you can call eating memory and displaying ads "working" anyway...
-
Well that was definitely it!
The "first bit" was never really designed/tested/etc against <object> tags, since those are never really embedded. Well, except that one time.
-
@morbiuswilters said:
It looks fine to me. Maybe you guys should get a real browser.
It looks correct to me. The browser is displaying it exactly as it's told to.(Edit; nothing quite like having your own WTF on your own site about WTFs eh Alex...)
-
It's fixed, great. ;)
/me hopes that it was fixed in some properly WTF-y way - like a magic "cut here" trigger that doesn't look like one, but is something innocent like a stray style="color: inherit;" in a following div.
-
You guys actually go to the front page?
