On 1/24/07, Jeff Shell <[EMAIL PROTECTED]> wrote: > > I have a question about the following admonition in the MochiKit.Signal > documentation (first block in the 'Overview' section). > > > When using MochiKit.Signal, do not use the browser's native event API. That > > means, no onclick="blah", no elem.addEventListener(...), and certainly no > > elem.attachEvent(...). This also means that MochiKit.DOM.addToCallStack and > > MochiKit.DOM.addLoadEvent should not be used in combination with this > > module. > > This *do not use* rule -- will events go kablooey if used together? > Say, if one is using other Javascript code (other big libraries, > widgets like TinyMCE, small personal chunks of code, etc) and it's > using the `addEventListener` / `attachEvent` system on its own, will > MochiKit.Signal interfere at all? > > Or once using Signal, am I limited to using *only* that? I intend for > all of our code (if I go this route) to use Signal exclusively. I just > want to make sure that I don't lock myself out of using other tools and > libraries.
If you're using Signal, you shouldn't attach the same events to the same nodes by other means. Behavior is undefined in that case. It might work, it might not. Attaching different events to the same nodes, or any events to other nodes should be fine. -bob --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MochiKit" group. To post to this group, send email to mochikit@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/mochikit?hl=en -~----------~----~----~----~------~----~------~--~---
