Skip to main content

Bug Tracker

Side navigation

#10548 closed bug (invalid)

Opened October 20, 2011 04:45PM UTC

Closed October 20, 2011 07:08PM UTC

val(value) does not send change events

Reported by: Owned by:
Priority: undecided Milestone: None
Component: unfiled Version: git
Keywords: Cc:
Blocked by: Blocking:


This is rather surprising.

It's possible to work around in your own code by manually sending the event, but this may not be possible if the relevant val(value) call is in third-party code. (For example: I want to trigger a function whenever a Calendrical widget updates a date input field, and I can't.)

Attachments (0)
Change History (1)

Changed October 20, 2011 07:08PM UTC by dmethvin comment:1

resolution: → invalid
status: newclosed

The browser's native behavior is to *not* fire events when the value property is changed. Thus we'd be introducing a difference from native behavior. Also, it would mean that changing the value of an input within the change event handler (for example, reformatting it) would cause infinite recursion.