PDA

View Full Version : Custom Scrollbar - Firefox/Netscape Bug



Rangler
03-26-2007, 01:07 AM
1) Script Title: Page Scroller (aka Custom Scrollbar)

2) Script URL (on DD): http://dynamicdrive.com/dynamicindex2/pagescroller.htm

3) Describe problem:

I have a long page at the USO of Northern Ohio (http://usocleveland.org) and really like this script. However, when you left click on either arrow using Firefox 3.0.0.1 or Netscape 8, you get an error console (View Screen Capture Here (http://www.ohiowebs.com/capture.htm)}. This doesn't happen in IE 7 or Opera 9. I created a page with no other scripts on it and it still happens. Plus, it happens here at DD link.

My concern is that if someone clicks on it and gets the error console, they may think their computer is under attack (:) ).

I was able to sustitute another arrow which I like but that didn't make the problem dissappear.

jscheuer1
03-26-2007, 07:13 AM
Looks like an actual bug. This should fix it:


<a href="javascript:up();" onclick="return false;" onmouseover="myspeed=-thespeed" onmouseout="myspeed=0"><img
src="arrows_up.gif" border="0"></a><br>
<a href="javascript:down();" onclick="return false;" onmouseover="myspeed=thespeed" onmouseout="myspeed=0"><img
src="arrows_dn.gif" border="0"></a>

Notes: The dark red additions are just to affect the status bar or other link report(s) of the browser to give the user a better idea of what the controls do. Just about anything can go there. The bright red additions are the real fix, preventing the browser from executing the href attribute onclick which would otherwise produce the error you are seeing.

Rangler
03-26-2007, 01:22 PM
Looks like an actual bug. This should fix it:


<a href="javascript:up();" onclick="return false;" onmouseover="myspeed=-thespeed" onmouseout="myspeed=0"><img
src="arrows_up.gif" border="0"></a><br>
<a href="javascript:down();" onclick="return false;" onmouseover="myspeed=thespeed" onmouseout="myspeed=0"><img
src="arrows_dn.gif" border="0"></a>

Notes: The dark red additions are just to affect the status bar or other link report(s) of the browser to give the user a better idea of what the controls do. Just about anything can go there. The bright red additions are the real fix, preventing the browser from executing the href attribute onclick which would otherwise produce the error you are seeing.

That did it. Thanks a lot! :)