Glad to see this get added. This adds another nice feature to, now non
element objects can be bound to events being triggered globally.
$({}).bind('listenup', console.log);
$.event.trigger('listenup', ['eh?']);
This unfortunately does not work in 1.2.6.
On Tue, Jul 1, 2008 at 5:16 PM, Ariel Flesler <[EMAIL PROTECTED]> wrote:
>
> The donative can be false, or anything else (true).
> So undefined will act as true, that's why I just omitted it.
> As for the extra it is used when coming from $.fn.trigger and
> $.fn.triggerHandler. Both add 'elem' so it won't fall on this case.
>
> This implementation should be alright.
>
> --
> Ariel Flesler
> http://flesler.blogspot.com/
>
> On 1 jul, 11:17, "mike.helgeson" <[EMAIL PROTECTED]> wrote:
> > I don't know about all of the specifics in the jquery event model, but
> > it seems to me like this call should include two more arguments:
> > "donative" and "extra"
> >
> > jQuery.event.trigger( type, data, this.handle.elem );
> >
> > jQuery.event.trigger( type, data, this.handle.elem, true, extra );
> >
> > The original call to was basically
> >
> > $('*').trigger( type, data )
> >
> > which ends up calling
> >
> > jQuery.event.trigger( type, data, this, true, fn );
> >
> > So "donative" was previously set to true, and maybe should be again
> > for consistency? The "extra" fn argument was dropped in the previous
> > implimentation because it ended up being undefined, but I don't think
> > it needs to be... although I don't really know what it is for as it is
> > not documented.
> >
> > On Jun 30, 10:28 pm, Ariel Flesler <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> > > Ok, done.
> >
> > > --
> > > Ariel Fleslerhttp://flesler.blogspot.com/
> >
> > > On 30 jun, 16:43, "mike.helgeson" <[EMAIL PROTECTED]> wrote:
> >
> > > >http://dev.jquery.com/ticket/3107
> >
> > > > On Jun 30, 2:19 pm, "John Resig" <[EMAIL PROTECTED]> wrote:
> >
> > > > > That sounds great to me, Mike! Feel free to post a follow-up ticket
> -
> > > > > we'll definitely tackle both of these for the next release. Great
> > > > > work.
> >
> > > > > --John
> >
> > > > > On Mon, Jun 30, 2008 at 12:57 PM, mike.helgeson <
> [EMAIL PROTECTED]> wrote:
> >
> > > > > > I don't know if anyone has experienced a performance issue with
> global
> > > > > > event triggering, but in my opinion the jquery core should not
> ever
> > > > > > call jQuery("*") internally.
> >
> > > > > > After investigating this unloading issue:
> >
> > > > > >http://dev.jquery.com/ticket/2698
> > > > > >
> http://groups.google.com/group/jquery-dev/browse_thread/thread/bdb96e...
> >
> > > > > > ...I noticed another potential bottleneck with the global event
> > > > > > triggering on line 1985 in 1.2.6 (uncompressed)
> >
> > > > > > jQuery("*").add([window, document]).trigger(type, data);
> >
> > > > > > I think this should be replaced by:
> >
> > > > > > jQuery.each( jQuery.cache, function(){
> > > > > > if ( this.events && this.events[type] )
> > > > > > jQuery.trigger( type, data, this.handle.elem, true );
> > > > > > });
> >
> > > > > > Opinions?- Ocultar texto de la cita -
> >
> > > > - Mostrar texto de la cita -- Ocultar texto de la cita -
> >
> > - Mostrar texto de la cita -
> >
>
--
http://morglog.alleycatracing.com
Lets make up more accronyms!
http://www.alleycatracing.com
LTABOTIIOFR! ROFL! ROFL! ROFL!
Upcoming alley cats, reviews, touring logs, and a general congregation of
bike nerdity.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
