the latest version (due to be released any day now) allows for selective event capturing.

if you do not require mouse events, there is no problem.  if you don't even use the event listeners, it might be possible to exclude the events.js file from your include section.

the events code for the API is actually a series of code hacks that allow us to takeover the processes normally handled by the browser.  since each browser has a different method of processing, it is required that we do this to make them all behave in the same fashion.

the next release has a more stable events structure and will hopefully avoid such problems as you have described.

Abre Chase wrote:

 Hello everyone!I'm using the 2001.01.25 release...I was running into an issue with my project where the DynAPI was always returning true on onClick events in hrefs.I need to have <a> links that call JS functions through the onClick event, but then return false so the link is never reached.  I simply can't get around the necessity to support this feature, because of legacy data.So I simply commented out the following line of code in dynapi.js:if (DynAPI.document.captureMouseEvents) DynAPI.document.captureMouseEvents();What effect might this have?  Why do we need to capture all events for the page?Anyway, this seems to have solved my problem as all the DHTML still behaves appropriatly in NS4.5, NS6, and IE5 - and href onClicks can now return false.I just wondered if someone could let me know why the DynAPI works in this manner.Thanks!- Abre
_______________________________________________ Dynapi-Help mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/dynapi-help

Reply via email to