You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to be able to use radio-inputs for some settings.
In my opinion that would be useful for little "switch-settings" like for example "enable/disable custom scrollbar".
Also, as currently I am using dropdowns for these two options, this would save the user 1 click :-)
As Mark attempted in #176 with the multi-select checkboxes, I also ran into the same JS-issue.
Jako also stumbled upon the exact same issue modxcms/revolution#12177 some time ago.
I will prepare a PR for my own feature-request here, and I am attempting a PR on the actual issue in the MODX code.
The text was updated successfully, but these errors were encountered:
### What does it do?
This makes sure the JS doesn't throw an error in the case that the
items-object is an array, just like in
#16404 for 3.x
### Why is it needed?
When using ExtJS to create components of the xtype: 'radiogroup' to be
used in CMPs inside a form,
this function gets called and tries to iterate over it's items array
with a method that doesn't exist.
This PR isn't changing the way forms or the clearDirty-method are
handled, it just assures no error is thrown when using
radiogroup-components.
### Related issue(s)/PR(s)
Resolvesmodmore/ClientConfig#202Resolvesmodmore/ClientConfig#176Resolvesmodmore/ClientConfig#143
---------
Co-authored-by: Jason Coward <[email protected]>
I would like to be able to use radio-inputs for some settings.
In my opinion that would be useful for little "switch-settings" like for example "enable/disable custom scrollbar".
Also, as currently I am using dropdowns for these two options, this would save the user 1 click :-)
As Mark attempted in #176 with the multi-select checkboxes, I also ran into the same JS-issue.
Jako also stumbled upon the exact same issue modxcms/revolution#12177 some time ago.
I will prepare a PR for my own feature-request here, and I am attempting a PR on the actual issue in the MODX code.
The text was updated successfully, but these errors were encountered: