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
Just raising my concern about using a mulitselect field that doesn't have a caret (or cross icon) to indicate that it also has a dropdown. @ScopeyNZ explained potentially because this has text auto complete. I also have concerns about the placeholder text "Select Some Options" due to the contrast for accessibility purposes. We discussed that this is a bug in framework and to raise an issue there which I'll add this week.
In the meantime for CKAN I think it's worth talking about some alternatives we could use such as using something like tagfield which has a dropdown caret and cross icon.
We discussed that this is a bug in framework and to raise an issue there which I'll add this week.
Yeah, I think that's where we should change this pattern. At this stage we're using existing form fields from core, I don't think there's a reason to create new ones - we should update the core ones if needed (being mindful that they'd flow on to all places they're used - which is a good thing I guess).
In the meantime for CKAN I think it's worth talking about some alternatives we could use such as using something like tagfield which has a dropdown caret and cross icon.
To be honest, introducing an extra module dependency in order to achieve this seems pretty low value to me. I think we'd be better to change the multi select design in core instead.
FWIW the core form field is ListboxField here, and this isn't a React form field - the issue we'd need to push forward would be silverstripe/silverstripe-admin#52. TagField already uses the same underlying library, so you'd end up with the same result except it would be in core instead.
Just raising my concern about using a mulitselect field that doesn't have a caret (or cross icon) to indicate that it also has a dropdown. @ScopeyNZ explained potentially because this has text auto complete. I also have concerns about the placeholder text "Select Some Options" due to the contrast for accessibility purposes. We discussed that this is a bug in framework and to raise an issue there which I'll add this week.
Designs for what we envisioned.
In the meantime for CKAN I think it's worth talking about some alternatives we could use such as using something like tagfield which has a dropdown caret and cross icon.
Any thoughts welcome.
All form designs can be found in our Styleguide
The text was updated successfully, but these errors were encountered: