- Issue created by @besek
- ๐จ๐ฆCanada joelpittet Vancouver
We encountered this issue and investigated further. It turns out the problem is not limited to the Gin themeโalthough Gin does interfere with things somewhat. Even when using other admin themes, the
#states
visibility logic for the min and max input fields is not applied correctly.Specifically, the
data-drupal-states
attribute is not being attached to the correct element. In the case of the Gin theme, it's being rendered on a wrapping<div>
instead of the actual<input>
elements for the min and max fields. And without the Gin theme, they don't have thedata-drupal-states
attribute at all!As a result, the visibility behaviour breaks: instead of hiding just the inputs when the selected operator doesn't require them (e.g., not using "Between" or "Not Between"), the entire filter may hide unexpectedly (Gin theme), or the fields may appear when they shouldn't (all the other themes).
- ๐จ๐ฆCanada joelpittet Vancouver
Somewhat related to ๐ Undefined array key "#type" in Drupal\Core\Form\FormHelper Active
- ๐จ๐ฆCanada joelpittet Vancouver
Postponing this on ๐ Undefined array key "#type" in Drupal\Core\Form\FormHelper Active please see if the latest MR resolves this issue for you.