Putting the rel attribute there tells the script to add its own onclick event to that tag, overwriting any that you had hard coded. Now in the configuration section of the main chrome.js file, there is:
Code:
//Chrome Drop Down Menu v2.01- Author: Dynamic Drive (http://www.dynamicdrive.com)
//Last updated: November 14th 06- added iframe shim technique
var cssdropdown={
disappeardelay: 250, //set delay in miliseconds before menu disappears onmouseout
disablemenuclick: true, //when user clicks on a menu item with a drop down menu, disable menu item's link?
enableswipe: 1, //enable swipe effect? 1 for yes, 0 for no
enableiframeshim: 1, //enable "iframe shim" technique to get drop down menus to correctly appear on top of controls such as form objects in IE5.5/IE6? 1 for yes, 0 for no
//No need to edit beyond here////////////////////////
dropmenuobj: null, ie: document.all, fir . . .
For links with rel attributes that are activated onmouseover, changing that to false may allow you to use your own hard coded onclick event. But it might not. What you could do though is add a span or a division and put your event on that:
Code:
<li><a rel="dropmenu1"><span onclick='alert("Test onClick event fired");'>TEST</span></a></li>
Some additional styles may be required to get it to look the same and/or to represent the same trigger area as it would without the added span. If your a tag has an href (your example does not) you may find it advantageous to add return false; to your onclick event:
Code:
<li><a rel="dropmenu1"><span onclick='alert("Test onClick event fired");return false;'>TEST</span></a></li>
Bookmarks