@Scott Ok, that's an easy change (leave it or remove it). The question is, what's the formal application of this extra function ?
@Diego We don't have the needed hacks to implement event capturing in IE (I know your NWEvents does). We don't plan to add that I think, that requires a lot of hacking and not many would benefit from it. So why add that parameter to our method ? I've been thinking about trying native event triggering instead of what we have now. I showed that old experiment where I achieved native event bubbling on all browsers, even for custom events. But that required quite a large amount of code, maybe we can leave that as a plugin. About the event properties from the originalEvent... jQuery "claims" it normalizes event objects in a cross browser way (some properties). Telling the user "look for them on the original object" doesn't seem too nice for me. Thanks both for replying. Cheers On Sat, Nov 29, 2008 at 1:08 PM, Scott González <[EMAIL PROTECTED]> wrote: > > jQuery UI uses the return value of triggerHandler, but we only care > about false, so this change shouldn't affect us. > > What's the logic behind removing the event from the extra function? > If I remember correctly, I talked to John about this a while ago and > he couldn't think of any reason why that was done. I created a ticket > to remove this behavior and it has just been sitting in Trac for 5 > months ( http://dev.jquery.com/ticket/3096 ). > > > On Nov 28, 7:14 pm, Ariel Flesler <[EMAIL PROTECTED]> wrote: >> Feedback please! :) >> >> I really like (and support) this feature. >> >> http://dev.jquery.com/ticket/3662 >> >> Also... I know that the returned value from jQuery.fn.trigger is used >> here and there (jQuery UI?). But that behavior is really odd and >> fragile in my opinion (false overrides any previous value). >> >> I think it'd be nice to return true/false depending on whether >> e.preventDefault() was called. This would be very useful for custom >> events, to allow event handlers to stop a scheduled (custom) behavior. >> >> As an alternative, we could add e.isDefaultPrevented() that retrieves >> this value from the event object. >> >> Note that none of this last 2 behaviors (or the one in the ticket) is >> my invention. >> I'm just imitating AS3's event system. I suppose that belongs to some >> EcmaScript specification as well. >> >> http://docs.brajeshwar.com/as3/flash/events/Event.html >> >> Thanks >> >> -- >> Ariel Fleslerhttp://flesler.blogspot.com > > > -- Ariel Flesler http://flesler.blogspot.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
