182477 - regression - dhtml menus (coolmenus) don't show up, reporting obj.addEvents is not a function

Status: RESOLVED FIXED

(Core :: DOM: Core & HTML, defect)

Description

[Vincent Deconinck]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2) Gecko/20021126

The page at http://www.indo-chine.org/disco uses Coolmenus v3.2 (from
http://www.dhtmlcentral.com ) to display inter-frames dhtml menus.
With Moz1.2, the menu frame remains blank, and the status bar says the following :
"There seems to be an error with this layer:#Frame: [object Window]#Layer:
divoCMenu0_0b.divoCMenu0_0" (note : I'm using '#' here instead of the "square"
graphic character displayed by Moz)

The javascript console gives the following error :

Error: obj.addEvents is not a function
Source File: http://www.indo-chine.org/disco/coolmenus3.js
Line: 318

Please note that the exacts same page worked for years in Mozilla up to 1.2b
included, and still works in nightly builds from the trunk (tested
2002-11-27-08-trunk).

The webmaster (me) is willing to correct its page if it has errors, but if it's
a CoolMenus problem, it probably occurs on many pages using this free script.

Reproducible: Always

Steps to Reproduce:
1. Go to http://www.indo-chine.org/disco with Mozilla 1.2 (release version)

Actual Results:  
There's no menu in the frame above

Expected Results:  
There should be a menu there, as you can see with Moz1.2b-, Moz trunk, IE4+ or NS4.x

Comment 1

[Torben]

Confirming with 1.2, will try with a trunk build later today.

Anyone know how 1.2-only bugs should be threated? WFM since they are not present
in trunk builds and I doubt there will be a 1.2.1?

Comment 2

[Torben]

Yep, works with trunk build 2002112607

Comment 3

[Frederic Bezies]

WFM - 2 hours old CVS based build (trunk) - WinXP-Sp1.

No problem at all for me.

Are you using any 3rd party theme ?

Comment 4

[Vincent Deconinck]

I don't use any special Theme. Tried with both modern and classic with same
results: Error on Moz v. 1.2 release only. OK with all other releases tested up
to now.

Comment 5

[James Graham]

This sounds like bug 182500 (1.2 branch only), or a dependency thereof. It looks
like there has been a problem just before shipping.

Comment 6

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

My testing confirmed that this is bug 182500.

Comment 7

[David Baron :dbaron: (⌚️UTC-4, no longer working on Mozilla)]

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.