Closed (fixed)
Project:
Drupal core
Version:
10.3.x-dev
Component:
Claro theme
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
3 Aug 2020 at 22:22 UTC
Updated:
2 Aug 2024 at 21:54 UTC
Jump to comment: Most recent, Most recent file




Comments
Comment #2
kostyashupenkoNot sure if we have to provide a fix for extrasmall modifier
Comment #3
KondratievaS commentedTested patch from #2 for mobile and desktop resolutions in Chrome, FF, Safari and IE browsers. Result is OK
Comment #4
KondratievaS commentedComment #5
bnjmnmThis approach changes the widths of the fields so an autocomplete with
size="60"would result in a different with than a text field withsize="60". This either needs to be addressed or we'd need design+maintainer approval on making this change.Comment #6
sd9121 commentedComment #7
sd9121 commentedComment #8
akshay kashyap commentedPlease tell the step to reproduces this issue. I have try to reproduces this issue but not able to reproduces.
Comment #9
bnjmnmTo reproduce: first, take a look at the screenshot in the issue summary, that is what you are going for.
With Claro as your theme, find a form with an autocomplete input, such as a tags input that accepts multiple values. Type a bunch of letters into the autocomplete input To fill it to the point that it fills the input all the way to the magnifying glass. Type what you see in the screenshot and that would work.
Comment #10
boulaffasae commentedI got the following erros when applying patch #2
Therefore, i couldn't create an interdiff.
I created a new patch based on the #2, i added
marginto fix the issue at #5.Comment #11
ressaGreat work everyone, the text no longer appear underneath the magnifying glass icon, but stops before. Also, the tag and text fields have the same width.
Comment #12
lauriiiMaybe we should make it specific that this is to accommodate the magnifier icon. Maybe something like
--form-autocomplete-magnifier-side-paddingwould work?We should have RTL rule for this.
We need
/* LTR */comment here because these styles are overridden in the RTL styles.Comment #13
komalk commentedWorked on #12.
Comment #14
bnjmnmRTL does not look right. I suspect this at least partly has to do with the RTL right margin style being a copy of the LTR one instead of one to accommodate RTL styling.
Comment #15
sd9121 commentedComment #16
sd9121 commentedPlease review this patch.
Thanks!
Comment #17
sd9121 commentedI have updated this patch, please review.
Thanks!
Comment #18
bnjmnm@sd9121 can you provide interdiffs with your patches? https://www.drupal.org/documentation/git/interdiff
Comment #19
sd9121 commented@bnjmnm, I have uploaded interdiff of patch #16 and #17
Please review.
Thanks!
Comment #20
meena.bisht commentedComment #21
meena.bisht commentedPatch #17 works good to me . Both when we insert from ltr and rtl. Below adding the screenshot.
Comment #22
meena.bisht commentedComment #23
meena.bisht commentedComment #24
ambuj_gupta commentedComment #25
ambuj_gupta commentedTest Steps:
1. Instal Drupal 9.1
2. Enable Claro Theme.
3. Apply the patch 3163127-17.patch
3. Create Article Content type.
4. Add long text(100 characters) in tags field and check.
Results:
Tested and verified after applying the patch 3163127-17.patch. And its working as expected.
Comment #26
ambuj_gupta commentedComment #27
lauriiiWhere does 2.5625rem come from? Should this be calculated based on --input-padding-horizontal and the icon size?
We should rename this using the same pattern. This would become
--form-autocomplete-magnifier-side-margin.Comment #28
sarvjeetsingh commentedI have updated the patch after replacing
--form-autocomplete-side-marginto--form-autocomplete-magnifier-side-margin.I am not sure about the first recommendation, @lauriii, can you provide a lil more information about that?
Comment #30
ranjith_kumar_k_u commentedI have tested the above patch on 9.2.x dev version ,the patch works fine for claro theme.
.RTBC
Before patch
After Patch
Comment #31
ranjith_kumar_k_u commentedRe-rolled from #28
Comment #32
djsagar commentedPatch #31 is applied and working on 9.2.x-dev.
I have tested claro theme.
Thanks!
Comment #33
bnjmnmThe patch in #31 has a "custom commands failed" message, which means it failed initial code quality checks, and automated tests didn't even run. Those need to be addressed before this can be RTBC. For more info on what needs to be addressed, clicking the message with "Custom Commands Failed" in it will take you to a report that summarizes why and includes info on how to run the tests locally.
It would be additionally helpful to have the before and after screenshots to have the same text content in the intputs. In the after screenshot it's not clear if there was enough text in the input to even cause overflow, especially since it ends with a period.
Comment #34
abhisekmazumdarFixed the "custom commands failed" issues. Kindly review
Comment #35
abhisekmazumdarComment #36
abhisekmazumdarMissing one check. Updated the patch.
Comment #37
djsagar commentedCustom commands failed please re-work.
Comment #38
djsagar commentedfixed custom commands failed issue please review.
Comment #40
sakthivel m commentedApplied the patch #38 on 9.3.x and it works fine. Adding screenshots below.
Moved to RTBC
Comment #41
sakthivel m commentedComment #42
lauriiiWe should still address #27. It's important that we document what that value is based on so that if someone is updating the designs, they know how to recalculate that value.
Comment #45
ameymudras commentedAs per the comment #27, calculating the padding using available variables
Comment #46
sonam.chaturvedi commentedVerified and tested patch#45 on 9.5.x-dev. Patch is applied successfully.
Test Steps:
1. Enable Claro Theme.
2. Apply the patch
3. Create Article Content type.
4. Add long text in tags field
5. Verify autocomplete input text does not visibly overflow under magnifier icon
Test Results:
Autocomplete input text does not visibly overflow under magnifier icon for Claro theme.
Before Patch:

After Patch:

Moving to RTBC
Comment #47
sonam.chaturvedi commentedComment #49
akshayadhavComment #50
akshayadhavRe-uploading the patch with minor fix. Ran code check locally which came out clean.
Comment #51
Manibharathi E R commentedPatch #50 tested and Applied successfully on Drupal 9.5.x.
Before patch:

After Patch:

Comment #52
akshayadhavComment #53
bnjmnmWe're good on screenshots now. A review of the code would be the next step.
Comment #54
nikhilraut commentedComment #55
nikhilraut commentedVerified and tested patch#50 on 9.5.x-dev. Patch is applied successfully.
Test Steps:
1. Enable Claro Theme.
2. Apply the patch
3. Create Article Content type.
4. Add long text in tags field
5. Verify autocomplete input text does not visibly overflow under magnifier icon
Test Results:
Autocomplete input text does not visibly overflow under magnifier icon for Claro theme.
Comment #56
vinaymahale commentedVerified and tested patch#50 on 9.5.x-dev for me. The patch is applied successfully.
Comment #57
vinaymahale commentedComment #58
bnjmnm@nikhilraut and @vinaymahale I just said in #53 we're all set on screenshots but need code review, then in #55 and #56 you both provide the opposite: screenshots without code reviews. These won't receive issue credit.
Comment #60
nod_D10 version needed
At this time we need a D 10.1.x patch or MR for this issue.
Comment #61
sahil.goyal commentedHi, reroll the patch for the version 10.1.x and attaching the reroll_diff
Comment #62
Ankit.Gupta commentedComment #63
nod_The last patch doesn't apply
Comment #64
pradhumanjain2311 commentedAs patch #62 is not applied i trued to fix patch #61.
by using yarn build.
Comment #65
deepalij commentedVerified patch #64 on Drupal 10.1.x-dev.
Patch applied cleanly.
Autocomplete input text is looking fine now in both LTR and RTL
Refer to the attached screenshots
RTBC +1
Comment #66
gaurav-mathur commentedApplied patch #64 works fine now text in input not overflow the icon on Drupal 10.1.x-dev
Refer to the screenshot
Comment #67
manojkumar_97 commentedComment #68
bnjmnmThis can be refactored so the RTL portion is not needed: change
margin-righttomargin-inline-endand changepadding-righttopadding-inline-end. The RTL additions and the/* LTR */annotations won't be needed after that.Comment #69
_utsavsharma commentedMade changes as per the comment #68.
Please review.
Comment #70
_utsavsharma commentedComment #71
bnjmnmChanging the margins and padding to use -inline-end instead of -right make all of this rtl styling unnecessary. That's why it was requested in the first place.
Comment #72
gauravvvv commentedI have updated the
margin-right with margin-inline-endandmargin-left with margin-inline-startand same for padding. Attached interdiff for same. Please review.Comment #73
gauravvvv commentedComment #74
nitin shrivastava commentedTry to fix ccf error in #72
Comment #75
bnjmnmThe benefit of using margin-inline and padding-inline
is that it's no longer necessary to add dedicated RTL styles. Inline margin/padding account for ltr/rtl automatically. It's a good idea to look up what impacts a suggested change will have instead of just carrying out the request - it's always possible it's a bad suggestion, even from me 😛
By using margin-inline and padding-inline in .js .form-autocomplete, you don't need to add anything for [dir="rtl"], and you actually break the styling if you do add it.This is just replacing padding and margin with
padding-inlineandmargin-inline. They aren't 1:1 replacementsComment #76
kristen polThanks for the work on this issue.
@gaurav-mathur Please check the comments to see if testing is needed. If it has been tested, you don't need to retest. This is a waste of everyone's time. Thanks.
@manojkumar_97 Please don't move to RTBC if the patch has been tested but the code hasn't been reviewed. Thanks. See the core gates here:
https://www.drupal.org/node/1203498
Comment #77
bunty oberoiI have created a Patch for the Autocomplete input text can visibly overflow under the magnifier icon. Please Review
Comment #78
akram khanadded updated patch and fixed ccf #77
Comment #79
akram khantry to fixed CCF #78
Comment #80
bnjmnmIf you look at the end of the Custom Commands failed output it provides instructions on running the checks locally so you can be assured it works before uploading a patch to an issue.
Here's an excerpt:
Comment #81
gauravvvv commentedUpdated short hand properties in #74, Attached interdiff for same.
Comment #82
bunty oberoiHi Gauravvvv,
The patch applied cleanly.
Autocomplete input text is looking fine now Here are the screenshots.
Comment #83
bunty oberoiComment #84
smustgrave commentedRemoving credit for bad rerolls
This appears to need an issue summary also.
Comment #86
vinaymahale commentedAny more work needs to be done here?
Comment #87
vinaymahale commentedComment #88
chi commented@smustgrave what needs to be updated in the issue summary?
Comment #89
smustgrave commentedIS is incomplete, no steps to reproduce, proposed solution, if UI change screenshots are needed.
Comment #90
shweta__sharma commentedIssue summary updated.
Comment #91
smustgrave commentedStill has TBD in the proposed solution.
Comment #94
scott_euser commentedComment #95
bnjmnmSee MR
Comment #96
scott_euser commentedThanks! My CSS is poor at best (was more helping to move forward) but thankfully simple enough change for me :) Confirmed, changing
<html>dir attribute to rtl and it looks fine still after this change.Comment #97
scott_euser commentedDoes this mean we should move the calc's from
:root {into the
.js { & .form-autocomplete {?
Comment #98
scott_euser commentedI think yes looking at other pcss files in core, so I have gone ahead and done that.
Comment #99
utkarsh_33 commentedAdded LTR and RTL views after the changes.
Comment #100
smustgrave commentedRemoving issue summary tag as that appears to be updated in #94
Applying the MR I'm getting the same results as the after screenshots provided in the summary and see all threads are resolved.
LGTM
Comment #102
nod_Committed and pushed 90f8dd194f to 11.x and 351c0873ee to 11.0.x and f9e6633c9a to 10.4.x and 42a97ff4f7 to 10.3.x. Thanks!
Comment #107
nod_