Closed
Bug 183199
Opened 22 years ago
Closed 15 years ago
Rollover pop-up menus fail
Categories
(SeaMonkey :: General, defect)
SeaMonkey
General
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jturiel, Assigned: asa)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130 Build Identifier: Mozilla 1.2.1 release (MacOS X 10.2.2) The WWE site uses Javascript to implement pop-up menus for site navigation. Using Mozilla 1.2.1 (and earlier 1.2 builds) on Windows 2000 and Windows XP, the menus function as designed. On the MacOS X build, these menus fail to appear when moused over. This occurs with and without the "Open unrequested windows" user preference checked, and works on Windows either way. Reproducible: Always Steps to Reproduce: 1.Load "http://www.wwe.com" on MacOS X version of Mozilla 1.2 or 1.2.1 2.Mouseover navigation bar 3.Watch the fun, or lack thereof. Actual Results: Nothing. Expected Results: Displayed site navigation menus, like the Windows version does. Here's the HTML code that builds the menubar: <map NAME="WWE_Navbar"> <area SHAPE="RECT" COORDS="0,0,53,28" HREF="javascript:void(0)" onmouseover="popUp('WWE_Menu1',event)" onmouseout="popDown('WWE_Menu1')" onclick="return false" title="NEWS"> <area SHAPE="RECT" COORDS="53,0,85,28" HREF="javascript:void(0)" onmouseover="popUp('WWE_Menu2',event)" onmouseout="popDown('WWE_Menu2')" onclick="return false" title="Pay Per View"> <area SHAPE="RECT" COORDS="85,0,110,28" HREF="javascript:void(0)" onmouseover="popUp('WWE_Menu3',event)" onmouseout="popDown('WWE_Menu3')" onclick="return false" title="Television"> <area SHAPE="RECT" COORDS="110,0,196,28" HREF="javascript:void(0)" onmouseover="popUp('WWE_Menu4',event)" onmouseout="popDown('WWE_Menu4')" onclick="return false" title="Superstars"> <area SHAPE="RECT" COORDS="196,0,269,28" HREF="javascript:void(0)" onmouseover="popUp('WWE_Menu5',event)" onmouseout="popDown('WWE_Menu5')" onclick="return false" title="Shopzone"> <area SHAPE="RECT" COORDS="269,0,315,28" HREF="javascript:void(0)" onmouseover="popUp('WWE_Menu6',event)" onmouseout="popDown('WWE_Menu6')" onclick="return false" title="Video"> <area SHAPE="RECT" COORDS="315,0,371,28" HREF="javascript:void(0)" onmouseover="popUp('WWE_Menu7',event)" onmouseout="popDown('WWE_Menu7')" onclick="return false" title="Live Events"> <area SHAPE="RECT" COORDS="371,0,451,28" HREF="javascript:void(0)" onmouseover="popUp('WWE_Menu8',event)" onmouseout="popDown('WWE_Menu8')" onclick="return false" title="Magazines"> <area SHAPE="RECT" COORDS="451,0,536,28" HREF="javascript:void(0)" onmouseover="popUp('WWE_Menu9',event)" onmouseout="popDown('WWE_Menu9')" onclick="return false" title="Interactive"> <area SHAPE="RECT" COORDS="536,0,620,28" HREF="javascript:void(0)" onmouseover="popUp('WWE_Menu10',event)" onmouseout="popDown('WWE_Menu10')" onclick="return false" title="Corporate"> <area SHAPE="RECT" COORDS="620,0,716,28" HREF="javascript:void(0)" onmouseover="popUp('WWE_Menu11',event)" onmouseout="popDown('WWE_Menu11')" onclick="return false" title="Sweepstakes"> </map></tr>
Comment 1•22 years ago
|
||
must be bad browser-sniffing JS code: http://www.wwe.com/js/wwe-loader-avm.js
Comment 2•22 years ago
|
||
Reassigning to Browser-General until we can get further information. Note the "loader file" loads these JS files used by the site: http://www.wwe.com/js/wwe-menu-avm.js http://www.wwe.com/js/wwe-menuvars-avm.js <--- this does the browser-sniffing: WWE_DOM = (document.getElementById) ? true : false; WWE_IE = (document.all) ? true : false; WWE_IE4 = WWE_IE && !WWE_DOM; WWE_IE5 = WWE_IE && WWE_DOM; WWE_Mac = (navigator.appVersion.indexOf("Mac") != -1); WWE_IE5M = WWE_IE5 && WWE_Mac; WWE_IEW = WWE_IE && !WWE_Mac; WWE_IE4W = WWE_IE4 && WWE_IEW; WWE_IE5W = WWE_IE5 && WWE_IEW; WWE_NS = navigator.appName == ("Netscape"); WWE_NS4 = (document.layers) ? true : false; WWE_NS6 = navigator.vendor == ("Netscape6"); if(WWE_IE5M) {WWE_DOM = false;WWE_IE4 = true} Josh: thank you for such a detailed report. It's good that you've tried a 1.2.1 build. We had to release that to correct a bad problem in 1.2 that prevented certain DHTML menus from working properly on any platform. See bug 182500. A couple questions: 1. Do the popup menus fail on OSX with trunk Mozilla builds, also? Do you know if the menus ever worked on OSX with Mozilla? 2. On OSX, when the menu fails, are you getting any errors in Tools > Web Development > JavaScript Console? (be sure to clear it of any previous errors first)
Assignee: rogerl → asa
Component: JavaScript Engine → Browser-General
QA Contact: pschwartau → asa
Reporter | ||
Comment 3•22 years ago
|
||
Here is the error I get on the (MacOS X) console: Error: uncaught exception: Permission denied to set property Window.status It has worked with some trunk builds in the past, but I apologize for not recalling exactly when and which. There was a period early in the 1.2 process when it didn't work on Windows, either. I neglected to file a bug report then. -Josh
Comment 4•22 years ago
|
||
Josh: thanks. That error makes this sound like bug 174224, "Permission denied to set property Window.status. Dropdown menus doesn't work" Notice the problem there turned out to be a stale Mozilla pref on the user's machine. This issue is fully explained in bug 117707, "Disabling 'Change status bar text' pref for JS breaks applications" In particular, see bug 117707 comment #93. Deleting the preference user_pref("capability.policy.default.Window.status", "noAccess"); from the prefs.js file solved the problem for the user in bug 174224. Note you may have other prefs files, too, called "all.js" or "user.js". There is also a GUI for this pref off the Mozilla menu: Edit > Preferences > Advanced > Scripts & Plugins There you will see a box enabling JavaScript to "Change status bar text". If this box is unchecked, it will cause the exception you're seeing. So check this box in the GUI, and then manually verify that you don't have the line quoted above in prefs.js, all.js, or user.js. Another thing to try is to create a new Mozilla profile altogether. If the Profile Manager doesn't come up automatically when you start Mozilla, you can force it to, by launching Moz from a console: [(path to Mozilla)] ./mozilla -profilemanager When the Profile Manager comes up, click on "Create Profile". Then see if the problem goes away -
Reporter | ||
Comment 5•22 years ago
|
||
Performing the prefs edit suggested had the following effect; The Error: uncaught exception: Permission denied to set property Window.status message still appears. However, now the status bar reads javascript:void(0) on mouseover events.
Comment 6•22 years ago
|
||
Josh: 1. So even after doing the prefs edit, the pop-up menus still fail on the OSX box? 2. Do you get the "Permission denied" error on Windows, too? If you get the error on Windows, but the pop-up menus work there, then I guess it was an unrelated problem -
Reporter | ||
Comment 7•22 years ago
|
||
On Windows, I get the following message: Error: element has no properties Source File: chrome://cookie/content/cookieNavigatorOverlay.xul Line: 128 And the same javascript:void(0) on the status bar. However, the menus work. I'm using the Modern theme on Windows, by the way.
Comment 8•22 years ago
|
||
So on Windows you don't get the "Permission denied" error? Then maybe that is the culprit here after all. I just can't figure out why you would get that on Mac OSX, but not on Windows. Have you tried creating a brand-new profile on the OSX box?
I don't see any rollover popup menus on Linux with latest trunk nightly too (2002121622) Here is the exception I get. (I have all the setting of status bar text enabled!) Error: uncaught exception: Permission denied to set property Window.status
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 10•22 years ago
|
||
Based on Tom's findings on Linux, changing Summary, and changing Hardware/OS: Macintosh/MacOS X ---> All/All.
OS: MacOS X → All
Hardware: Macintosh → All
Summary: Rollover pop-up menus fail, but only on MacOS X platform (AFAIK) → Rollover pop-up menus fail; (only on MacOS X and Linux?)
Comment 11•21 years ago
|
||
I have contacted the WWE.com about this problem. I included all the needed info such as the operating system, a summary and also included a link to this bug report and the comments. If anymore info needs to be relayed to the WWE about this problem please go here http://shopzone.wwe.com/webapp/wcs/stores/servlet/shopzone/KANA/WWEContactUs.jsp?MAJOR_GROUP_ID=TECHNICAL_PROBLEMS&ACTION_ID=TECH_SUPPORT_WWE I have also recieved a response which goes as follows WWE.COM would like to thank you for helping us to improve our Web site. Many of these problems can be solved without replying to your e-mail, but if you do require a response, please allow 1-2 business days for a customer service representative to review your e-mail and respond accordingly. Thank you for your interest in WWE.COM. Sincerely, WWE.COM TECHNICAL TEAM
Updated•20 years ago
|
Product: Browser → Seamonkey
Comment 12•15 years ago
|
||
The last post here was six years ago. The web site is working fine in Seamonkey 2.0a3 and (FF) current trunk build Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2a1pre) Gecko/20090321 Minefield/3.6a1pre. The "More" menu on the website has a rollover menu, and that does work fine. Removing MacOS and Linux mentions from summary as per comment 10. Resolving WFM.
Summary: Rollover pop-up menus fail; (only on MacOS X and Linux?) → Rollover pop-up menus fail
Updated•15 years ago
|
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•