Closed Bug 151936 Opened 23 years ago Closed 9 years ago

fipa.org - Javascript roll-over images not working correctly

Categories

(Web Compatibility :: Site Reports, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jdale, Unassigned, NeedInfo)

References

()

Details

(Whiteboard: [js] [contactready] [clientsniff] )

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1a) Gecko/20020611 BuildID: 2002061104 The graphical links on the images in the middle of this page do not work; also, the Javascript roll-over images (which should change the mouse-over image to yellow) do not work either. Reproducible: Always Steps to Reproduce: 1. Go to http://www.fipa.org/repository/bystatus.html 2. Move the mouse of the 'Preliminary' graphic 3. Try to click on 'Preliminary' Actual Results: 1. When the mouse is moved over the 'Preliminary' graphic, nothing happens, but the cursor does change to the finger pointer 2. When the link on 'Preliminary' is clicked, the page does not open Expected Results: 1. When the mouse moves of the 'Preliminary' graphic, it should change to a yellow-highlighted image 2. When the link on 'Preliminary' is clicked, it should follow the link (this can be achieved with right-click and then 'Open in new window' If it helps, the Javascript for this site was developed with NetObjects Fusion MX, version 6.20.
it looks like the JS Code use Layers for Mozilla. Error: this.style.layers has no properties Source File: http://www.fipa.org/script.js Line: 39 I bet this is TE but I'm not sure.... but this is never a blocker Phil: Do you have 2 seconds for this ? (/me should learn JS)
Severity: blocker → normal
Should be TE. The HTML contains layers, and the JavaScript manipulates those layers to achieve the mouseover effects. The link is really an onClick event that doesn't work because of the Javascript errors (because layers don't exist in Mozilla).
Correct; reassigning to Tech Evangelism. The site does not sniff for Mozilla/N6/N7. All they do is check |navigator.appName|: var F_NN=navigator.appName=='Netscape'; Subsequent codepaths for Netscape rely on this, and include calls to layer functionality; for example, see the line below: function F_nn_mouseMove(e) { F_P2(e); if ((document.F_dragLayer != null) &&(document.F_dragLayer.length > 0)) { var d = document.F_dragLayer[0].layer; <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< if ((document.F_dragLayer.length == 1) && (d.fastDrag)) { var BA = d.Q4 - e.pageX; var BB = d.Q5 - e.pageY; d.Q4 = d.Q4 - BA; d.Q5 = d.Q5 - BB; d.offset(-BA, -BB); } else { F_drag(e.pageX, e.pageY); } return false; } }
Assignee: rogerl → doron
Component: JavaScript Engine → US General
Product: Browser → Tech Evangelism
QA Contact: pschwartau → zach
Version: other → unspecified
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Javascript roll-over images not working correctly → fipa.org - Javascript roll-over images not working correctly
tech evang june 2003 reorg
Assignee: doron → english-us
QA Contact: zach → english-us
I checked the description and today I got those expected results with my Mozilla 1.8a5
Tested today, still doesn't work.
Assignee: english-us → nobody
Component: English US → Desktop
Footer: © 2005 Foundation for Intelligent Physical Agents. All Rights Reserved. Please send comments to webmaster(at)fipa.org What the webmaster has been doing since 2005 I don't know.
Whiteboard: [js] [contactready] [clientsniff]
Hmm I have little hope the site will be fixed given the history of the bug, but the reporter of the bug seems to be the author of the site. <META NAME="Author" CONTENT="Jonathan Dale"> <META NAME="Generator" CONTENT="NetObjects Fusion MX for Windows"> So maybe he can help us understand the status of all this.
Flags: needinfo?(jdale)
Since the site author is the reporter and hasn't responded in 14 years, I'm going to close this issue as WONTFIX.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: Tech Evangelism → Web Compatibility
You need to log in before you can comment on or make changes to this bug.