Closed (fixed)
Project:
Webform
Version:
6.3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
13 May 2025 at 16:24 UTC
Updated:
11 Sep 2025 at 01:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
anpri31 commentedI'm also experiencing this issue after upgrading. Even when "Use timepicker" is disabled in the Webform time element, the jquery-timepicker still attaches to the input, which breaks native type="time" behavior and causes validation errors (e.g., "The specified value '12:03 AM' does not conform to the required format").
Is there any update or workaround available for this? We’d prefer not to switch the field type or rewrite the form structure.
Comment #3
cilefen commentedYou experienced this after upgrading specifically which versions of which software?
Comment #4
anpri31 commentedfacing this issue after upgrading to Drupal 11 & my webform version is 6.3.0-beta2
Comment #5
cilefen commentedWhat were the initial versions?
Comment #6
anpri31 commentedearlier version was 6.2.7 which was working fine
Comment #7
cilefen commentedgit log -S timepicker 6.2.7..6.3.0-beta2shows that #3495674: Fix broken tests and #3461552: Require minimum of Drupal 10.2 and remove compatibility shims are the changes affecting "timepicker" directly that are only in 6.3.Comment #8
liam morlandComment #9
pepeprawn commentedMy solution:
This patch makes two targeted changes:
Updates the JavaScript selector to only attach to input[type="text"] elements, preventing interference with native HTML5 time inputs
Only adds the data-webform-time-format attribute when #timepicker is explicitly TRUE
Testing:
Tested on Drupal 11.0.5 with Webform 6.3.x
Confirmed that with "Use timepicker" disabled, native HTML5 time inputs work correctly
Confirmed that with "Use timepicker" enabled, jQuery timepicker functions as expected
Form submissions work properly in both modes
This is a minimal change that maintains backward compatibility while fixing the reported issue.
Comment #10
dmitrii puiandaikin commentedGot the issue after upgrading to Drupal 11, the patch has fixed the issue
Comment #11
abrammFaced the same issue, the patch from #9 worked well.
Moving to RTBC.
Comment #12
daletrexelJust chiming in to say that we're running patch from #9 in production and it seems to be working fine for us.
Comment #13
liam morlandThanks for the patch. Please put the patch into an issue fork and merge request.
Comment #22
robijntje94 commentedSorry for the inconvenience. Everything wasn't working properly. I have no credits on this one.
Comment #23
liam morlandDoes the patch not apply? I do not seen any commits on the merge request branch,
3524216-jquery-timepicker-setting.Comment #25
jrockowitz commentedComment #27
jrockowitz commentedThis feels very safe moving to RTBC if tests pass
Comment #29
jrockowitz commented