User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2) Gecko/20021126 Wasn't there/a problem in 1.1 Installed 1.2.....getting errors: There seems to be an error with this layer: Frame:[object Window] Layer:divoCMenu0_0b.divoCMenu0_0 followed by: There seems to be an error with this layer: Frame:[object Window] Layer:divBillyMenu0_ob.divBillyMenu0_0 Note, a "menu bar" is missing from the top of the page Reproducible: Always Steps to Reproduce: Go to website: www.ulead.com Actual Results: see above error messages.......... Expected Results: Work as expected, without errors..... Did not have this problem with Mozilla 1.1 Works in IE 6 and Netscape Communicator 4.77

This site works fine for me using a Mozilla trunk build on WinNT from 2002-11-27. This is another manifestation of Parser bug 182500, which affects 1.2 builds only. Adding dependency and reassigning to Parser for parity -

Thanks for the confirmation. Pulled down latest nightly build (1.3a). Issue seems to be resolved in it.

I have tested that this bug was an instance of bug 182500 / bug 182253 based on comparison of two Linux builds compiled with gcc 3.2. This bug was present in the 1.2 release and was the only bug fixed in the 1.2.1 release (and the reason for the 1.2.1 release). Marking this bug as fixed since it should be fixed in the 1.2.1 release.

Well, this is sortof fixed in 1.2.1 but not completely or this could simply be another issue. Go to www.ulead.com using both 1.2.1 and 1.3a. While 1.2.1 does not crash like 1.2 did, it is missing something. Half the screen/graphics/options are not there in 1.2.1 while it looks correct in 1.3a.

Zolatan: Have you cleared the disk cache before you reopend this bug ?

No, I did not realize I needed to clear the cache. I tried refresh numerous times, thinking it would clear it, that way. Yes, force clearing the cache resolved it. Sorry to be annoying.

v fixed (after reporters comment) you got a corrupted document in the cache because of the 1.2 bug. YOu could also do a shift+reload (Reload without shift reloads the document from teh cache) to get it working agai.