I get a JS error: http://a372.g.a.yimg.com/f/372/27/1d/www.geocities.com/js_source/ygNSLib6.js line 46: document.yl0 has no properties when I load this from Geocities. When I load it from a local file after saving, I get no error and it seems to be ok (the geocities stuff shows up 'correctly'). This seems to apply to many/most geocities sites (not all have the same footer).

Using Mozilla tip build 2000-07-24 4PM Pacific Time on WinNT. Have to mark this one as invalid, as the HTML page in question uses layers, which were supported in NN4.7, but are not supported in Mozilla. I get the reported error on WinNT, even when I download locally: http://www.geocities.com/NapaValley/Cellar/3517/r_storepizza.html http://a372.g.a.yimg.com/f/372/27/1d/www.geocities.com/js_source/ygNSLib6.js To see the problem, note that some of the HTML is written dynamically by the file ygNSLib6.js. For example, it defines a constant: ycL0='<layer pageY=0 pageX=0 visibility=hidden name='; and then tries to make this an HTML element on the page with the name 'yl0' : document.write(ycL0+'yl0>' + etc. etc. This would work in NN4.7 but will not work in Mozilla. Hence the object document.yl0 is undefined; hence the error line 46: document.yl0 has no properties For W3 standards and the differences between Navigator 4.x and Mozilla, see http://sites.netscape.net/ekrock/standards.html For Nav4 info, see http://developer.netscape.com/docs/technote/dynhtml/csspapi/csspapi.html Also see http://www.mozilla.org/newlayout/bugathon.html#layerbugs

Randell, thank you for reporting this: in particular, your comment that This seems to apply to many/most geocities sites (not all have the same footer)

Marking Verified -

Adding "[LAYER]" to Summary for tracking purposes -

Moving all [LAYER] bugs to Evangelism component for tracking and open-source evangelism by mozilla community members of sites that need to upgrade to support web standards such as HTML 4.0 (instead of LAYER/ILAYER) and the W3C DOM (instead of Nav4 document.layers[] or IE document.all()). Sites should be lobbied to do the upgrade using the email templates that are linked to from http://www.mozilla.org/newlayout/bugathon.html#layerbugs . When a site's owner has confirmed receipt of the message requesting an upgrade, the bug should be marked with the keyword evangelized to indicate that evangelism for that bug is complete. When the site finishes the upgrade and supports standards, the bug should be closed.

Closing all Evangelism bugs where no evangelism is needed because page has been fixed, site is internal to Netscape, report is a DUP, or bug report is no longer appropriate for evangelism for any other reason.

I just rechecked this site on geocities. They're still using layers for the site footer/whatever. Is this a dup? If so, fine, otherwise I think it should remain an open evangalism item - geocities is a BIG site, and they use this footer for quite a few of the member's pages.

Good catch Randall. REOPENing. This kind of analysis and input by mozilla community members is exactly what I hoped the Evangelism component would achieve. Thanks!!!

SPAM:Changing QA contact on 111 evang bugs as I am now the new QA contact for this component. Sorry about the spam zach

Reassigning Evangelism bugs to me, the component's new owner. I would like to take this opportunity to thank nobody@mozilla.org for all of his dedication, contributions, and hard work, and wish him luck at his new job. Thanks, nobody.

How, did we lose the QA contact on this bug? Changing it back to zach.

-> evangelism@telocity.com for my evangelism bugs. removing the now-depreciated evangelism-related keywords. setting platform to All.

Reassigning evangelism bugs to bclary@netscape.com.

I'd say, it's fine if Mozilla doesn't display Geocities Ad Square correctly. But it gets bad, if Mozilla crashes when I try to close the Ad Square by clicking the [X] on the top right corner. URL: http://www.geocities.com/nadine_ruppen/ STDOUT: JavaScript error: http://us.geo1.yimg.com/us.geocities.com/js_source/ygNSLib9.js?v3 line 40: document.yl0 has no properties Document http://www.geocities.com/nadine_ruppen/ loaded successfully ./run-mozilla.sh: line 72: 1032 Speicherzugriffsfehler $prog ${1+"$@"} I'm running Mozilla/5.0 (X11; U; Linux 2.4.0-4GB i686; en-US; rv:0.9+) Gecko/2001051306

I found out, that mozilla crashes, because it can't DNS resolve the hostname us.toto.geo.yagoo.com. Is this a javascript DNS lookup bug?

*** This bug has been marked as a duplicate of 84101 ***

All Evangelism Bugs are now in the Product Tech Evangelism. See bug 86997 for details.

v