313093 - Attempting to use JS menus blanks much of page, prevents any further URL loads

Status: VERIFIED DUPLICATE of bug 312563

(Camino Graveyard :: Page Layout, defect, P2)

Description

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

Some folks over on the mZ forum have discovered a pretty nasty bug on Adobe.com:
http://forums.mozillazine.org/viewtopic.php?t=331724

STR:
1. Load http:/www.adobe.com
2. Mouse over one of the JS menus (Products, Solutions, Support, Purchase)
3. Attempt to load another URL via any means, anywhere in Camino.

Results:
JS menu not drawn, SWF animation and other parts of the page whited out, Camino
unable to load any URL in any tab/window/new window/etc. via any means (forever
"Loading..." and blank pages.  Quitting Camino is required.

I think it's branch-only, but it's not always clear who's using what.

Everything works fine in tonight's Fx branch nightly, and Camino 0.8.4 worked
properly, too, except occasionally the .swf would duplicate itself lower in the
window when mousing over the JS menus.  I diffed the pages served to Camino and
Fx and they were identical, but I didn't check any of the external JS files for
browser-sniffing.

Comment 1

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

The external JS seems to be just their stats/tracking stuff from what I can tell.

Comment 2

[Smokey Ardisson (offline for a while; not following bugs - do not email)]

I think this might be an unfixed part of the recursive widget bug (bug 312563).
 I tried a nightly from the 14th (before the RW fix) and got the red highlight
under the JS menu and then the beachball, a la the RW.

We don't know when the RW bug first appeared; the first mention of it was my
comment on 10-11 in bug 308802.  The last comment I made in that bug before
getting the RW was 9-28.  I tried that nightly, and Adobe.com worked properly.

Comment 3

[Simon Fraser [no longer active]]

Yes, my hunch is bug 312563 too.

Comment 4

[Simon Fraser [no longer active]]

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