- Issue created by @andybroomfield
Does reverting/reversing https://git.drupalcode.org/project/drupal/-/commit/8905837f693c4f0341dd9... on its own fix this?
- 🇬🇧United Kingdom andybroomfield
@cilefen yes, i'm able to get it working with the states.js file from Drupal 10.2 inside of an otherwise 10.3 site.
I commented 🐛 #states not working correctly when built from a logical combination of multliple fields Fixed there.
- 🇮🇳India sukr_s
Looks like a related issue 🐛 JS #states behavior does not have a detach method Needs review
I have a patch that removes the once call from #3386191. This will break that fix, of course, but if you didn't have that problem, then this will fix what that broke. It seems that a more complicated patch will be required to fix both issues.
- 🇺🇸United States jrockowitz Brooklyn, NY
Marking as major and waiting to see how this addressed via Drupal core.
- 🇬🇧United Kingdom steven jones
Out of interest does the fix for 🐛 States are processed and added to the wrong attribute since #1427838 Active help with this issue?
- Status changed to Postponed
29 days ago 2:13pm 24 December 2024 - 🇨🇦Canada karing 🇨🇦
Confirming this on our projects as well. We often do things like:
Add two Date fields and use a Computed Twig Element to calculate the Duration.
Only show the Submit button if the Duration is > 0 to prevent incorrect submissions.
Duration field is calculated properly (Computed Twig is correct).
However, the Submit button on the form is permanently hidden since D10.3 upgrade (last week).I see -> https://www.drupal.org/project/drupal/issues/3468860 🐛 JS #states behavior does not have a detach method Needs review - is a fix for D11 - it's marked Needs Review. There is also a note on that issue "Webform overrides some of the states API methods so any patch here will need an update on webform side".