Closed Bug 281395 Opened 21 years ago Closed 20 years ago

javascript drop down menus do not appear

Categories

(SeaMonkey :: General, defect)

Sun
Solaris
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: ylubarsky, Unassigned)

References

()

Details

(Keywords: qawanted)

User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.7) Gecko/20040615 Firefox/0.9 Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.8a6) Gecko/20050112 Each item of the top menu bar on the specified page should display a drop down menu when mouse hovers over it. Instead nothing is shown. The page works fine on Windows platform. This issue is reproducible with firefox 0.9 as well. Reproducible: Always Steps to Reproduce: 1.open the given url 2.mouse hover over one of the menu items - 'Products'/'Training&Services'/etc. Actual Results: The menu item highlights but no dropdown menu appears Expected Results: The menu item should highlite and a dropdown menu should appear.
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b) Gecko/20050207 Firefox/1.0+ Quickly looking at your page it seems to WFM. Could it be platform or OS specific? Do you have Javascript enabled?
Javascript is enabled. The page works fine on Windows so its definitely platform specific. I am using SunOS 2.8 OS Perhaps the funcitonality is dependant on some SUN patch ?
Check whether the page sends the same content on Windows and on Solaris?
Keywords: qawanted
Version: unspecified → 1.7 Branch
Version: 1.7 Branch → Trunk
Yackov: does the server send the same content to Windows and Solaris?
I have checked and indeed it seems that the content is different. In fact, on nt there is some extra javascript code for onmouse events that shows the menus and it is missing on unix page. It looks that this is the reason for the problem. I'll try and check whether adding the extra code for unix page solves this.
FWIW: the page works on MAC OS X
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.