Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.This meeting takes place every Tuesday, usually at 14:00 UTC (10:00am ET, 7:00am PT). See Time.is to see what that is in your timezone.
The meetings are held using Zoom, and a link is posted in the #ux Slack channel just prior. Agenda is first come, first serve and set by attendees. Use Needs usability review tag for issues that need review and/or suggest issues in comments here.
Recording of this week's meeting: https://youtu.be/HCUEg4Wwdvc
We discussed the following issue:
No one raised any usability concerns with switching to split buttons. We asked for a couple of changes to the issue summary:
- Under "Proposed resolution", mention the main visual difference between the two: when expanded, the drop button's primary option is part of the list, but in a split button it is not.
- Under "User interface changes", add "before" and "after" screenshots. There are already some screenshots in the comments, but none in the issue summary.
Comments
Comment #2
lauriiiI'd like to discuss #1899236: Add new Splitbutton render element to eventually replace Dropbutton
Comment #3
benjifisherComment #8
benjifisherComment #9
benjifisherComment #11
benjifisherComment #13
benjifisherComment #14
AaronMcHaleIs the recording for this one available yet?
Comment #15
andrewmacpherson CreditAttribution: andrewmacpherson as a volunteer commentedI'd like to see the recording of this one too.
Comment #16
benjifisherComment #17
AaronMcHaleJust catching up on the meeting recording, very pleased to see how far progress has come with the Split Button render element(s), this looks like a good improvement over the existing Dropdown Button element(s) and I agree overall with what was said during the meeting.
The only thing I wonder, during the meeting it was mentioned that any render elements could be added as items inside the drop-down area, examples were given of needing to put buttons inside the drop-down area, and for good reason. However, is there a risk that by given too much freedom, the UI can break? For instance, hypothetically a developer could decides to place a select render element as one of the items in the drop-down area. Am I understanding this correctly, and if so is this a problem that we need to be concerned about, or is it even a problem at all, is that "by design" so that we don't make any assumptions and we put the responsibility of fixing any broken UI on the developer?
Another specific thing I wanted to highlight, I do like the new behaviour of the Split Button element where the primary item is always highlighted as the primary item and not shown as part of the list. My thinking here is that, as a developer or designer I'm making an active decision to say which of these items is the primary item because (presumably) I know that this is the most valuable one in the majority of cases, I wouldn't expect that to change when the drop-down area is open, therefor I don't have any strong objections to just loosing the behaviour of the "legacy" drop-down/drop-button because I don't think it adds any real value compared with the value that the new Split Button element adds. Besides, as highlighted, if I really have a use-case for all items being treated equally, I can just use the option where the button is just a toggle.
TLDR: new one is great, covers enough common use-cases, I think the old pattern can safely be retired.
Great work everyone!
P.S. This comment has also been posted on the issue at #1899236-137: Add new Splitbutton render element to eventually replace Dropbutton, please reply directly on that issue.