Skip to main content

Bug Tracker

Side navigation

#5851 closed bug (fixed)

Opened January 18, 2010 02:54PM UTC

Closed January 27, 2010 03:07PM UTC

Last modified March 09, 2012 04:39PM UTC

IE8 does not support the change event while using live

Reported by: matiasnu Owned by: brandon
Priority: major Milestone: 1.4.2
Component: event Version: 1.4.1
Keywords: Cc:
Blocked by: Blocking:

According to

The change and submit events work reliably across browsers for both normal and live events. We override the normal change and submit events in Internet Explorer and replace them with events that work identically to the other browsers.

This is not true for IE8, which seems to ignore live bound change events. (is I use bind, it works as advertised, though)

Attachments (4)
  • changetest.html (0.4 KB) - added by simonjefford January 18, 2010 04:41PM UTC.

    Simpler test case

  • changetest141.html (0.3 KB) - added by matiasnu January 26, 2010 12:52PM UTC.

    Same test case but with 1.4.1

  • testcase14-bind.html (1.5 KB) - added by matiasnu January 18, 2010 02:55PM UTC.

    Using bind and change works in IE8

  • testcase14-live.html (1.5 KB) - added by matiasnu January 18, 2010 02:55PM UTC.

    Using live and change does not work in IE8

Change History (10)

Changed January 18, 2010 03:15PM UTC by matiasnu comment:1

This text should also be changed until the bug is fixed;

All Events Can Be Live Events

With the exception of ready, focus (use focusin instead), and blur (use focusout instead), all events that can be bound using .bind() can also be live events.

We’re very proud to count some addtional events amongst those supported by live(). 1.4 introduces cross-browser support for

change, submit, focusin, focusout, mouseenter, and mouseleave via the event delegation in .live().

Changed January 18, 2010 04:40PM UTC by simonjefford comment:2

I'm seeing the same thing here. Support for all events in live() across all the major browsers was the reason we just upgraded.

Changed January 18, 2010 10:46PM UTC by trixi comment:3

I have already posted a possible fix in the old discussion-group:

I have looked into this. The "trigger-line" in the testChange-function

has to be changed from this:

return jQuery.event.trigger( e, arguments[1], this );

to this:

return jQuery.event.trigger( e, arguments[1], elem );

Additional It seems, that there was a typo. The condition above

contains the following statement:

elem.type !== "select"

wich is always true. I think this can be deleted, without problems.

Some further infos about what is causing the bug, can be also found in the post:

Changed January 18, 2010 10:53PM UTC by john comment:4

resolution: → fixed
status: newclosed

Changed January 26, 2010 12:51PM UTC by matiasnu comment:5

resolution: fixed
status: closedreopened

It seems that 1.4.1 does not detect the first change on an element in IE8 but the following changes work as expected. (attaching @simonjefford test case using 1.4.1 instead)

Changed January 26, 2010 04:29PM UTC by parrots comment:6

Problem seems to be in the testChange function. It's is using to cache the value of the input. The first time called it tries to get the previous value and it's undefined since it hasn't been cached yet. It returns without triggering the event because of the if check that fires because it's undefined. The next time through the cache has been created for the element with it's previous value and it can evaluate the change properly.

Changed January 26, 2010 05:23PM UTC by parrots comment:7

Changing the beforeactivate function to the following seems to fix this issue in IE:

var elem =;

if (elem.nodeName.toLowerCase() === "input" || elem.nodeName.toLowerCase() === "textarea") {, "_change_data", getVal(elem));


Changed January 27, 2010 03:07PM UTC by john comment:8

resolution: → fixed
status: reopenedclosed

Changed January 27, 2010 03:07PM UTC by john comment:9


Changed February 15, 2011 09:29PM UTC by anonymous comment:10

This seems to be broken again in IE9