Closed (fixed)
Project:
Webform
Version:
7.x-4.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
2 Jun 2015 at 06:24 UTC
Updated:
26 Jun 2015 at 20:44 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
sumitmadan commentedThis should be a feature request. Adding a patch for this feature.
Comment #3
sumitmadan commentedComment #5
danchadwick commentedComment #6
szantol commentedThank you!
Lajos
Comment #7
danchadwick commentedIf the number component is configured as a list, I'm pretty sure the jQuery won't work correctly with significant changes, no? I'm not sure what other options might be problematic.
I didn't include number, date, and time in SET actions for this reason.
What has been tested?
Comment #8
sumitmadan commentedIt is working fine without any jquery issue. But I have a doubt, It is disabling the field after setting the value. So in case of select list, if there is no value to set then it will disable the select list with no value.
Please close if there is an issue to keep this feature for number component.
Comment #9
danchadwick commentedI am okay with the user needing to set reasonable values.
It is proper for the form element to be disabled when it is being set. There is no point in letting the user change the value when webform will just set it back again.
@szantol -- Thanks for the patch. It makes it easier for me if they are named according to the Drupal standard:
https://www.drupal.org/patch/submit
Committed to 7.x-4.x and 8.x.