Closed (outdated)
Project:
Webform
Version:
7.x-4.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
31 May 2018 at 23:59 UTC
Updated:
23 Sep 2025 at 14:08 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
mirakolous commentedI am attaching a patch that resolves my specific issue. Hopefully this can make its way into the module at some point. I am not sure what the downside is, yet.
Comment #3
liam morlandI don't know of any reason for change not being triggered.
Comment #4
geoffreyr commentedI've been looking into doing some work with conditionals as well, and this applies to text fields as well. Since changes to text fields aren't applied through
$.webformVal(), and since$.webformVal()is only used duringDrupal.webform.doConditions, I'm taking the alternate approach of triggering a change event on all applicable selects and text fields after the value has been updated.This appears to be pretty essential for making it work well with Webform Calculator formulae.
Comment #5
varshith commentedI agree @geoffreyr
But I think it would be better if only trigger a 'change' when 'actionResult' is set. That way we only do it when we actually set values and not otherwise. I have an updated patch attached.
Comment #6
liam morlandThere will need to be a comment in the added code documenting why it is there.
Comment #7
mirakolous commentedThis patch still applies for me. I have added a comment to it. Let me know if the wording should change and I can adjust.
Comment #8
liam morlandThanks. Please add a period to the end of the comment, check your indentation, and put the patch in an issue fork.
Comment #9
liam morlandDrupal 7 is no longer supported. If this applies to a supported version, please re-open.