Bug Tracker

Ticket #6964 (closed bug: wontfix)

Opened 5 years ago

Last modified 4 years ago

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:
Blocking: Blocked by:


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.

Change History

comment:1 Changed 5 years ago by mspreij

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?

comment:2 Changed 5 years ago by dmethvin

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.

comment:3 Changed 4 years ago by dmethvin

  • Priority set to undecided
  • Status changed from new to closed
  • Resolution set to wontfix

This seems like it has to be fixed by Chrome.

Note: See TracTickets for help on using tickets.