* TITLE/SUMMARY Javascript on Fishcam page completely broken on Gecko * STEPS TO REPRODUCE 0) Go to http://www.netscape.com/fishcam * RESULT - What happened Instead of the school of animated yellow fish taking a leisurely swim around my web page, Gecko presented the two fish stationary, enlarged and pixelated. One fish was scaled to the size of (and presented within) the small Fishcam viewer window, the other scaled to the size of (and presented within) the large Fishcam viewer window. Viewer frames could not be dragged around. *** Clicking on either of the two buttons (Refresh or Close) effectively kills Viewer (not crashed, but wholly dead otherwise. Scroll bar wouldn't respond, menus & the close/minimize maximize buttons didn't respond, yada, yada.) - What was expected * REGRESSION - Occurs On viewer.exe (12.30.98 Win32 build used) - Doesn't Occur On Communicator 4.5 for Win32 (RTM Complete build used) IE 4.0 for Win32 (had its own problems with the script, but different ones..) * CONFIGURATIONS TESTED - Windows NT 4.0 SP 3, 96 MB RAM.

As this is a javascript bug, I think it's probably yours. If not, I'll move it to a javascript person. Please advise.

There are no plugins or Java on this page so I'm reassigning this to a JS person. I tried assigning this to Clayton Lewis, but it seems he doesn't have a bugzilla account. Vidur - can you assign this to the right person? Thanks!

It's probably the layers code on the page that's the root of the problem. We're not quite there with layers and there's no schedule for when we might be. Troy, it is a bit surprising that some of the layers show up initially, even though they should be hidden.

Setting all current Open Critical and Major to M3

Setting all LAYER bugs to M15 for as-time-allows evangelism.

Have notified Netcenter. INVALID. LAYER, ILAYER, document.layers[] not supported in Gecko/Nav5. Closed.

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.

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.

workaround bugzilla problem that caused a bunch of evangelism bugs to be NEW/INVALID, NEW/FIXED, NEW/WORKSFORME or NEW/DUPLICATE

Marking invalid. Site has changed.

vrfy invalid

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