Problem/Motivation
The "Filter by keyword" input is cut off:

This was first reported in #3328566: The placeholder in webform filter input is not displayed correctly but the text was shortened and worked at the time but this no longer appears to be the case.
Steps to reproduce
Go to /admin/structure/webform
Proposed resolution
Increase the max-width on the element. Override Claro's negative margin on autocomplete elements so the next element isn't pulled over.
Remaining tasks
N/A
User interface changes
Filter by keyword input is no longer cut off.
API changes
N/A
Data model changes
N/A
| Comment | File | Size | Author |
|---|---|---|---|
| #9 | After_Patch.png | 308.59 KB | sdhruvi5142 |
| #9 | Before_Patch.png | 383.56 KB | sdhruvi5142 |
| #6 | webform-after.png | 19.66 KB | snehal-chibde |
| #6 | webform-before.png | 19.56 KB | snehal-chibde |
Issue fork webform-3509604
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 #3
mjpa commentedWasn't the max-width, but Claro adding a negative margin-inline-end which was pulling the next element inwards.
The MR resolves this and with it applied, we now see:
Comment #4
mjpa commentedComment #5
snehal-chibde commentedComment #6
snehal-chibde commentedI have checked the issue on drupal 11, webform 6.3x, and applied the above MR. It is working fine. Added before and after screenshot below for reference.
Comment #8
snehal-chibde commentedComment #9
sdhruvi5142 commentedHi, Applied MR!601 on drupal 11.x version and it is working as expected.
Testing Steps:
1. Installed webform on my Local setup
2. Go to /admin/structure/webform
3. Observe the changes there..
Testing Result:
After applying patch the "Filter by keyword" isn't being cut off and there is proper space between both the filters and it looks as expected. And moving this to RTBC+1. Attaching screenshots for reference.
Status: PASS
Comment #10
sdhruvi5142 commentedComment #11
jrockowitz commentedI tested the fix in Chrome and Firefox and it looks good.