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
Description of the problem
I'm trying to add a "Statuses" field to an add-on, and it seems there is some native code styling a <fieldset id="fieldset-statuses"...> element different than a normal checkbox field, which is fine, except it does not render well. If I rename the field it renders the checkboxes as expected, but I would like to actually use the name "statuses" as it's a consistent with the naming scheme of other settings on this page (e.g. "tags", "items") .
How To Reproduce
In an add-on I'm creating a checkbox field with the name of "statuses" with this configuration
There is a whole set of styles for this since it's named "statuses" - I'm not sure where else in EE this is used. I'm fine if it renders different... but it should render well.
The text was updated successfully, but these errors were encountered:
I'm not sure this is fixed :( If there are just 2 statuses it's fine, but as soon as there are 4 or more options, it turns into a React field and renders oddly.
Description of the problem
I'm trying to add a "Statuses" field to an add-on, and it seems there is some native code styling a
<fieldset id="fieldset-statuses"...>
element different than a normal checkbox field, which is fine, except it does not render well. If I rename the field it renders the checkboxes as expected, but I would like to actually use the name "statuses" as it's a consistent with the naming scheme of other settings on this page (e.g. "tags", "items") .How To Reproduce
In an add-on I'm creating a checkbox field with the name of "statuses" with this configuration
Screenshots
Environment Details:
There is a whole set of styles for this since it's named "statuses" - I'm not sure where else in EE this is used. I'm fine if it renders different... but it should render well.
The text was updated successfully, but these errors were encountered: