341930 - washingtontimes.com - script type="text/javascript1.1"

Status: RESOLVED FIXED

(Tech Evangelism Graveyard :: English US, defect)

Description

[Paul Dickins]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.0.4) Gecko/20060508 Firefox/1.5.0.4

Hello,
The problem is described, with screen seizes, here:
http://mattoid.com/data/computing/need_to_have_clean_code.htm
What had happened originally, with the latest FireFox build, was a blank page, totally. This improved after a while, but still loads incorrectly. The comparison shows IE v FireFox, and the latest code source.
Paul

Reproducible: Always

Comment 1

[Régis Caspar]

Login/pass for URL: [e-mail]/bugmenot

From the ad script used (i.e.  http://oascentral.washtimes.com/RealMedia/ads/adstream_mjx.ads/insider.washtimes.com/front/1/1234567890@Top?):

document.write ('<!-- ---------- Advertising.com Banner Code -------------- --> \n');
....
document.write ('<!-- ---------- Copyright 2000, Advertising.com ---------- -->');

So Firefox behavior looks correct to me. see bug 214476#c4

Comment 2

[Phil Ringnalda (:philor)]

No, nothing to do with comment parsing (particularly since those appear to be properly balanced to actually work). The problem is that they have their browser sniffing that decides between using OAS_version 11 and 10 in a <script type="text/javascript1.1"> block, and while we know about type="text/javascript", and language="JavaScript1.1", we don't know how to execute a script with the type "text/javascript1.1", so we get the fallback OAS_NORMAL ad instead of the OAS_RICH ad, and the OAS_NORMAL ad is just an image with a big long script-built URL that redirects to Akamai serving a file named empty.gif that is, in fact, an empty 1x1 gif.

Comment 3

[Régis Caspar]

(In reply to comment #2)
OK. I probably made an error counting those --

Comment 4

[Chris Lawson (gone)]

Site's been totally redesigned and I can't even find any "Insider" sub-site any more. FIXED, as far as I'm concerned, since comment 2 shows a legitimate TE bug.