Skip to main content

Bug Tracker

Side navigation

#6964 closed bug (wontfix)

Opened August 27, 2010 11:28PM UTC

Closed October 03, 2010 08:32PM UTC

change(function() {..}) handler fires unnecessarily on Webkit

Reported by: mspreij Owned by:
Priority: undecided Milestone: 1.4.2
Component: event Version: 1.4.2
Keywords: change Cc:
Blocked by: Blocking:
Description

The .change() handler triggers only on actual changes in Firefox, but in Safari/Chrome it triggers also if you enter something in the field, then delete it, and then tab out of it - leaving the field the same as it was before, unchanged.

Attachments (0)
Change History (3)

Changed August 28, 2010 12:19AM UTC by mspreij comment:1

Ehrmmm.. so, it turns out that in Chrome at least, for

<input type="text" name="whatever" value="yadda" onchange="foobar()">

the foobar() function gets called also, without an *actual* change, just some editing and undoing and tabbing out. Webkit bug?

Changed August 28, 2010 02:51AM UTC by dmethvin comment:2

Well if Chrome/Webkit is firing the change event then jQuery will deliver it. A workaround at our level would require saving the current value on focus and then comparing to that value on blur. I'd file a bug with them.

Changed October 03, 2010 08:32PM UTC by dmethvin comment:3

priority: → undecided
resolution: → wontfix
status: newclosed

This seems like it has to be fixed by Chrome.