Problem/Motivation
This can happen
- At narrower widths
- When a dropbutton has more than one word (thus it has a space)
At certain viewport widths, the browser may add a line break between words, which results in the primary button having more height than the disclosure button next to it. The intent is for these heights to match. While this does not make the dropbutton unusable, it is not a visual experience that inspires confidence.

Steps to reproduce
1. Login as an Admin user.
2. Go to a page with a dropbutton that has a primary button with a label that includes at least one space such as "Manage Fields" in Home > Administration > Strucuture > Content types (admin/structure/types).
3. Switch to the tablet device view using inspect tool.
| Comment | File | Size | Author |
|---|---|---|---|
| #25 | 3321726-nr-bot.txt | 90 bytes | needs-review-queue-bot |
| #23 | 3321726-nr-bot.txt | 85 bytes | needs-review-queue-bot |
| #18 | After patch.png | 62.18 KB | Bushra Shaikh |
| #18 | Before patch.png | 66.62 KB | Bushra Shaikh |
| iOS-15.5.png | 227.88 KB | akshaydalvi212 |
Issue fork drupal-3321726
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
Comments
Comment #5
akshaydalvi212 commentedComment #6
hhvardan commentedThe change didn't fix the issue on real device because it make changes only for no-touchevent devices.
Probably you need to add the same style to the ".js .dropbutton--multiple .dropbutton__item:first-of-type" selector.
Comment #9
akshaydalvi212 commentedComment #10
gaurav-mathur commentedComment #11
gaurav-mathur commentedThe change fix the issue and it is working properlyin all devices. Refer to screenshots. please ignore second image(afterpatch.jpg) it's upload by mistake.
Comment #12
gaurav-mathur commentedRefer to screenshot.
Comment #13
hhvardan commented+1 RTBC
Comment #14
bnjmnm@gaurav-mathur given that the changes are to the Claro theme, and your screenshots are from Olivero, I'm not sure how that before/after could have happened but it's certainly not relevant to this issue
I left feedback in the MR that needs addressing
Also tagging with "Needs issue summary update" as this (seeming correctly) targets
.no-toucheventsstyles in the solution, which suggests it is an issue regarding multiword dropbutton content on narrower withs, and not something specific to tablets/touch devicesComment #16
ameymudras commentedComment #17
Bushra Shaikh commentedComment #18
Bushra Shaikh commentedVerified patch #16 on Drupal 10.0.x. Patch applied successfully and looks good to me.
The issue is fixed after applying the patch.
refer screenshot:
can be moved to RTBC+1
RTBC+1
Comment #19
smustgrave commentedMR looks good and fixes the issue but this was previously tagged for IS update in #14 which still needs to happen.
Comment #20
athyamvidyasagar commentedDrop down issue is fixed for D10. Patch and screenshots are attached.
Comment #21
bnjmnmHi @akshaydalvi212, are you familiar with Drupal's Gitlab integration? The patch you provided replicates work that is already in this issue's Merge Request, so it doesn't provide any additional value and would not receive credit. The contrib process can be confusing, especially with patches and Merge Requests both being valid ways to provide code changes in an issue. If the docs don't clear things up, it's usually possible to get additional guidance in Drupal slack, particularly if they are targeted questions vs requests for general assistance.
_______________
Issue summary updated.
Comment #22
bnjmnmComment #23
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #24
sourabhjainHidding the #20 patch files as we have already the MR. It is creating confusion.
Comment #25
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #26
bnjmnmThe bot switched this to needs work because patch #20 was not passing tests. However, there was already a test-passing merge request awaiting review, so I'm switching it back to that. Be sure to review the MR not any patches (thanks @sourabhjain for hiding those)
And no shade on Needs Review Queue Bot - you are a good and helpful bot.
Comment #27
smustgrave commentedCan the MR be rebased for 11.x and backported
Thanks.
Comment #28
nod_(bot was testing against 10.1.x, not 10.0.x might be why it complained)
Comment #31
sagarchauhan commentedRebased the MR for 11.x
Comment #32
smustgrave commentedReroll was good.
Comment #34
bnjmnmGood simple fix there. Committed to 11.x. Thanks folks!