Sorry Ariel, your right. I believe I must have been thinking about relatedTarget. :)
-- Brandon Aaron On Sat, Jan 31, 2009 at 6:02 AM, Ariel Flesler <[email protected]> wrote: > > No, currentTarget was a 1.3.x addition. I added it within trigger and > thought event objects had it in IE. > I realized I was wrong some days ago. I'll add it once I get back. It > should be done within $.event.handle. > > -- > Ariel Flesler > http://flesler.blogspot.com > > On 30 ene, 19:17, Brandon Aaron <[email protected]> wrote: > > I'm fairly certain we normalized this in pervious versions. Definitely a > > regression. Might want to file a ticket so it doesn't get lost on the > list. > > -- > > Brandon Aaron > > > > On Fri, Jan 30, 2009 at 11:51 AM, Arrix <[email protected]> wrote: > > > I'm not sure whether jQuery used to fix currentTarget for IE but I > think > > > it's not an easy task. The only way I know to get the currentTarget in > IE > > > is to use this keyword, which is only available in the ele.onxxx = func > > > model. > > > > > On Sat, Jan 31, 2009 at 12:53 AM, Jörn Zaefferer < > > > [email protected]> wrote: > > > > >> It looks like a regression to me: $.event.fix doesn't add > > >> currentTarget to the event object, which is missing in IE. Is that a > > >> regression? Or is there a reason it isn't added? > > > > > -- > > > Arrix > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
