i would also love to have bubbling available for custom events. i have several situations where i would use it immediately.
On Fri, Sep 19, 2008 at 5:10 PM, Dan Webb <[EMAIL PROTECTED]> wrote: > > On Sat, Sep 20, 2008 at 12:41 AM, Ariel Flesler <[EMAIL PROTECTED]> wrote: >> >> You wouldn't expect those events to bubble because they are referred >> to that solely element. > > Yes, this is an issue and I agree with your point about bubbling some > events not being as meaningful. > > There are lots of use cases for being able to bubble custom events. > I've used the technique heavily in Prototype and it's the reason I > wrote this patch. It's probably worth going with an opt in approach > when bubbling custom events because in many cases its very meaningful > for them to bubble. For instance, a whole raft of mutation events > could be added. 'domupdated', 'contentloaded' etc. It would just be a > case of fitting the option into the API. Maybe: > $(element).trigger(type, data, bubble); > > I'd love to see this go in to jQuery. It's an incredible useful way > of handling lower level events, bundling them into a useful high level > custom event then sending them up the DOM tree to be processed and is > much cleaner than attaching everything to the document. > > As an aside we should probably only bubble native events that normally > bubble to preserve expected behaviour. > > Thanks, > > -- > Dan Webb > http://www.danwebb.net > > aim: danwrong123 > skype: danwrong > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
