> It will stop plugins from interfering with each other. > > If a plugin has an error in its document.ready handler it will prevent > subsequent handlers from running. A bad plugin can affect other jQuery > code.
I don't buy that argument. If a plugin or other jQuery method is malfunctioning then the site is (by definition) breaking. Attempting to continue execution would likely only exacerbate the problem. There are so many other places where an exception can occur (especially during initialization, which is far worse). There's minimal benefit being provided here (continuing execution in an already-broken application) especially when compared to the severe overhead that this technique will incur. Instead of directly executing the function you must do an extra dispatch on every single bound function on every single event - including bubbling. Yikes! > Read the article again. People seem to be concentrating on the > document.ready problem. But the real solution is firing custom events > in MSIE. > > You may not see the point of it now. But I bet that you end up > implementing it. :-) The custom events in IE are kind of neat - but I don't really see how we could benefit from them. We already have a full custom event architecture - including supporting event bubbling, stopImmediatePropagation, and other W3C-compatible methods. --John --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
