Missing onmouseover and onmouseout events of an AREA element ...
Reported by juanzeta | May 29th, 2008 @ 01:31 PM
I've defined an image map using onmouseover and onmouseout events. Those events get lost when I include the effects.js library.
After some debugging, I guess the redefinition of the Object class forgets to add the funcionality in that type of element.
This error doesn't occur in Internet Explorer 6, but in Firefox 2 and 3, Safari and SeaMonkey.
Comments and changes to this ticket
-
Thomas Fuchs May 29th, 2008 @ 06:32 PM
- → State changed from “new” to “invalid”
There is no "redefinition of the Object class" in the libraries. Please include:
a) versions of Prototype and script.aculo.us you use
b) a working demo that shows the problem
You probably want to ask on the mailing list first. Closing the ticket.
-
juanzeta May 30th, 2008 @ 09:56 AM
Thanks for your quick response.
Sorry I was mixed up. I think it is the definition of the Element class, but it's only a guess.
My scriptaculous version is 1.8.1 which works with the 1.6.0.1 version of the prototype library.
I've attached a file containing the working demo:
There're two html files: prueba.html and prueba_wo.html. The first includes the effects library and skips the onmouseover event in the AREA element. The second goes without the effects library to check the functionality of the AREA events.
Thanks and congratulations for your great work.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
script.aculo.us is an open-source JavaScript framework for visual effects and interface behaviours.
Source available from github
The Git repository resides at:
http://github.com/madrobby/scriptaculous
Check out the current development trunk with:
git clone git://github.com/madrobby/scriptaculous.git
As script.aculo.us 1.xx is feature-frozen, this development trunk is for bugfixes only.
New development should happen only for
script.aculo.us 2.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post a an example that shows off the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
