Skip to main content

Bug Tracker

Side navigation

#7910 closed bug (invalid)

Opened January 06, 2011 01:29PM UTC

Closed January 30, 2011 08:02AM UTC

Last modified March 14, 2012 12:23AM UTC is maybe undefined i

Reported by: EMVI Owned by: EMVI
Priority: undecided Milestone:
Component: event Version: 1.4.4
Keywords: Cc:
Blocked by: Blocking:

in jQuery.event.special.change.filters.beforeactivate is maybe undefined



.trigger(new $.Event({ target: myElementNode, pe: 'focus' });

I fixed it in an external file, so I don't want modify the original source.

var _beforeactivate = jQuery.event.special.change.filters.beforeactivate;

jQuery.event.special.change.filters.focus = jQuery.event.special.change.filters.beforeactivate = function( e ) { = | | e.currentTarget | | e.originalTarget;



Attachments (0)
Change History (5)

Changed January 06, 2011 05:21PM UTC by rwaldron comment:1

owner: → EMVI
status: newpending

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced jsFiddle test case to help us assess your ticket!

Additionally, test against the latest jQuery release and the jQuery 0 GIT version to ensure the issue still exists. Be Excellent to eachother!

Changed January 06, 2011 05:22PM UTC by rwaldron comment:2

component: unfiledevent

Changed January 16, 2011 01:29AM UTC by EMVI comment:3

status: pendingnew

This error occurs only in one case so far.

There is a DomNode relates to some widgets and several events are bound.

I can't post this case, because this script depends an several scripts of my employer that are not allowed to publish.

Changed January 16, 2011 01:31AM UTC by rwaldron comment:4

status: newpending

Can you provide a reduced test case, that illustrates the bug using

Changed January 30, 2011 08:02AM UTC by trac-o-bot comment:5

resolution: → invalid
status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!