I just discussed this with Scott over IM, there are some issues that we can't account for (or hardly):
- It won't stop propagation of events that aren't bound via jQuery - It won't stop propagation of events that are bound on child nodes of the element in context On Fri, Feb 13, 2009 at 3:41 PM, Scott González <[email protected]>wrote: > We have a few places in jQuery UI where we need to prevent events from > occurring, e.g., preventing the click event after a drag. We've been > partially successful by just binding a handler and the click event and > returning false. This can be improved by calling > event.stopImmediatePropagation(), but that won't prevent handlers bound > before ours from running. The only solution I can come up with is to force > our handler to be the first handler. With some help from Ariel, I've put > togheter some code ( http://codedumper.com/oxewu ) and I'm looking for > some feedback. Is there some other way we can prevent event handlers from > running? Are there still caveats like native onclick events? > > > > -- Paul Bakaus UI Architect -- http://paulbakaus.com http://www.linkedin.com/in/paulbakaus --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
