I've added a new ticket for this patch:
http://dev.jquery.com/ticket/3401
On Tue, Sep 23, 2008 at 11:13 AM, Dan G. Switzer, II <
[EMAIL PROTECTED]> wrote:
> John,
>
> >That sounds reasonable - is there a bug/patch kicking around?
> >
> >event.triggered sounds like the right naming for this.
>
> Here's a patch that should work. Basically you just need to add the
> "triggered" key to the "fake" event and then when you define the timestamp
> event property also set the "triggered" to false.
>
> Index: Y:/.workspace/jquery/src/event.js
> ===================================================================
> --- Y:/.workspace/jquery/src/event.js (revision 5853)
> +++ Y:/.workspace/jquery/src/event.js (working copy)
> @@ -186,6 +186,7 @@
> // Pass along a fake event
> if ( event ) {
> data.unshift({
> + triggered: true, // flags that
> event
> was triggered manually
> type: type,
> target: elem,
> preventDefault: function(){},
> @@ -315,7 +316,10 @@
>
> // Fix timeStamp
> event.timeStamp = event.timeStamp || now();
> + // add flag that this has been triggered via an actual
> event
> + event.triggered: false;
>
> +
> // Fix target property, if necessary
> if ( !event.target )
> event.target = event.srcElement || document; //
> Fixes #1925 where srcElement might not be defined either
>
> -Dan
>
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
