Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.As far as I can tell, when the datapicker is used to change the value of a date field, it does not cause a 'change' event in that field.
Normally this isn't an issue, but if people want to associate an action with the change, then it doesn't seem to work :-(
Maybe I've missed something?
(I'm trying to get dates working with editablefields, which uses the change event).
Cheers
Mark.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | 348166-3.patch | 1.58 KB | Jelle_S |
Comments
Comment #1
markfoodyburton CreditAttribution: markfoodyburton commentedrubbish
my fault
sorry
Comment #2
theshanergy CreditAttribution: theshanergy commentedDid you ever get this working? I'm having a related problem with editable fields - see my issue here http://drupal.org/node/1079446
Comment #3
Jelle_SWe need this feature for Clientside Validation. Validation for fields fire on the change event, the datepicker changes the value of the field, but doesn't set the focus back on the field. Change events get triggered when a user clicks out of the input element and the value is changed, but since there is no focus on the element, no change event is triggered when the user clicks somewhere else, and thus no validation takes place. Attached is a patch to fix this.
Comment #4
Jelle_SComment #5
xatoo CreditAttribution: xatoo commented#3: 348166-3.patch queued for re-testing.
Comment #6
xatoo CreditAttribution: xatoo commentedAfter applying the patch I no longer get the timepicker popup. This message appears in the JS console instead.
Comment #7
afmdsouza CreditAttribution: afmdsouza commentedThanks for patch, works fine with 7.x-2.7.