Views Exposed Grouped Filter: Radio/select widget selection doesn't control widget when 'allow multiple selections' is checked [#2881541]

When creating a filter on a view (in my case for an integer field -- not sure where else this would apply) that is exposed, grouped, and set to allow multiple selections, the widget selector for 'radio' vs 'select' doesn't make a difference. If there are 4 or less options defined, the filter defaults to checkboxes; more than 4 options, and the filter defaults to a select list.

I'd imagine expected behavior is that this would change based on the selected widget type.

Comments

Comment #1

25 May 2017 at 20:39

mrweiner created an issue. See original summary.

Comment #2

mrweiner CreditAttribution: mrweiner as a volunteer commented 25 May 2017 at 21:14

For anybody coming across this who needs the checkbox functionality when only the select list is present, there's appears to be a handful of jquery scripts out there to handle conversion. Multicheck is working for me at the moment.

Comment #3

Lendude

Dutch

Amsterdam

CreditAttribution: Lendude as a volunteer and at Dx Experts commented 26 May 2017 at 06:25

Version:

8.3.2

» 8.3.x-dev

Bit of a split between a bug and a feature really.

But I never liked the hardcoded limit of 4, so taking that out and giving control to the widget selector would take some of the magical 'what just happened??' out of this.

If we do this, we would need an upgrade path for existing Views to make them default to the current behaviour.

Comment #4

mrweiner CreditAttribution: mrweiner as a volunteer commented 26 May 2017 at 22:23

Yeah it's does feel between a feature and a bug. I think the reason it feels like a bug is because the widget selector is available but not functional. If the widget weren't present, I don't think it would feel as buggy to me. Even just adding an explanation for the "magical" part of this and hiding the widget selector if "allow multiple selections" is selected would make it feel more like intended functionality.

Giving full control (as a feature request) would certainly be preferable overall. I'd be open to helping with this, but have no idea where to start. Never worked on something like this before.

Comment #5

26 May 2017 at 22:23

Version:

8.3.x-dev

» 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.