Problem/Motivation

If an autocomplete input's text fills the input, the text will appear underneath the magnifying glass icon.

This is also an issue in Seven, but may be less noticeable due to the size of the inputs and icons.

Steps to reproduce

  • Set the claro theme as an administration theme
  • Find a form with an autocomplete input field such as a tags input that accepts multiple values ( In my case I used the default tags field in
    article content type )
  • Type a bunch of letters into the autocomplete field to fill it to the point that it fills the input all the way to the magnifying icon.
  • See that the letters will overlap with the magnifying icon

Proposed resolution

Add margins and padding on either the right or left side depending on the text direction.

User interface changes

Before
before

After
LTR
LTR

RTL
RTL

CommentFileSizeAuthor
#99 LTR.png57.31 KButkarsh_33
#99 RTL.png56.89 KButkarsh_33
#96 2024-07-04_05-38.png14.78 KBscott_euser
#90 after.png75.29 KBshweta__sharma
#90 before.png265.63 KBshweta__sharma
#90 after.png75.29 KBshweta__sharma
#83 Screenshot from 2023-03-16 11-03-41.png28.04 KBbunty oberoi
#82 Screenshot from 2023-03-16 11-25-36.png20.21 KBbunty oberoi
#81 interdiff-74_81.txt2.85 KBgauravvvv
#81 3163127-81.patch4 KBgauravvvv
#79 interdiff_78-79.txt1.64 KBakram khan
#79 3163127-79.patch2.28 KBakram khan
#78 interdiff_77-78.txt1.51 KBakram khan
#78 3163127-78.patch2.35 KBakram khan
#77 3163127-77.patch1.66 KBbunty oberoi
#74 interdiff_72-74.txt1.33 KBnitin shrivastava
#74 3163127-74.patch3.46 KBnitin shrivastava
#72 interdiff_69-72.txt2.25 KBgauravvvv
#72 3163127-72.patch3.46 KBgauravvvv
#69 3163127-69.patch3.4 KB_utsavsharma
#69 interdiff_64-69.txt1.99 KB_utsavsharma
#66 after-patch-text-override-icon.png5.67 KBgaurav-mathur
#66 before-patch-text-override-icon.png5.99 KBgaurav-mathur
#65 After patch - RTL.png72.81 KBdeepalij
#65 Before patch - RTL.png79.12 KBdeepalij
#65 After patch - LTR.png72.44 KBdeepalij
#65 Before patch - LTR.png57.62 KBdeepalij
#64 3163127-64.patch3.42 KBpradhumanjain2311
#62 3163127-62.patch3.14 KBAnkit.Gupta
#61 reroll_diff_50-61.txt2.38 KBsahil.goyal
#61 3163127-61.patch3 KBsahil.goyal
#56 core-autocomplete-overflow.png9.12 KBvinaymahale
#55 After- Patch.png264.22 KBnikhilraut
#55 Before -Patch.png86.08 KBnikhilraut
#51 After-Patch-3163127-50.png95.26 KBManibharathi E R
#51 Before-Patch-3163127-50.png100.98 KBManibharathi E R
#50 interdiff_45-50.txt742 bytesakshayadhav
#50 3163127-50.patch3.06 KBakshayadhav
#46 afterpatch#45.png40.55 KBsonam.chaturvedi
#46 beforepatch#45.png45.1 KBsonam.chaturvedi
#45 3163127-45.patch3.06 KBameymudras
#40 After-patch.png142.45 KBsakthivel m
#40 Before-patch.png146.03 KBsakthivel m
#38 interdiff_36-38.txt1.78 KBdjsagar
#38 3163127.patch3.01 KBdjsagar
#36 interdiff.3163127.34-36.txt1.74 KBabhisekmazumdar
#36 3163127-36.patch3.01 KBabhisekmazumdar
#34 interdiff.3163127.31-34.txt3.02 KBabhisekmazumdar
#34 3163127-34.patch3.01 KBabhisekmazumdar
#32 before-patch.png30.26 KBdjsagar
#32 after-patch.png33.46 KBdjsagar
#31 3163127-31.patch3 KBranjith_kumar_k_u
#30 after---patch.jpg269.45 KBranjith_kumar_k_u
#30 before---patch.jpg244.72 KBranjith_kumar_k_u
#28 interdiff_17-28.txt1.43 KBsarvjeetsingh
#28 3163127-28.patch3.01 KBsarvjeetsingh
#25 after_patch.png198.36 KBambuj_gupta
#25 before_patch.png270.67 KBambuj_gupta
#22 Screenshot 2020-09-16 at 9.45.49 AM.png70.76 KBmeena.bisht
#21 Screenshot 2020-09-16 at 9.45.35 AM.png74.02 KBmeena.bisht
#19 interdiff_16-17.txt1.23 KBsd9121
#17 3163127-17.patch2.98 KBsd9121
#16 3163127-16.patch2.96 KBsd9121
#14 Screen Shot 2020-08-31 at 9.17.50 AM.png52.05 KBbnjmnm
#13 3163127-13.patch2.93 KBkomalk
#13 interdiff_10-13.txt3.02 KBkomalk
#11 3163127-11-text-tags-field-width.png26.79 KBressa
#10 3163127-10.patch2.79 KBboulaffasae
#5 Screen Shot 2020-08-05 at 11.38.50 AM.png338.79 KBbnjmnm
#3 selected_9650.png106.5 KBKondratievaS
#2 3163127-2.patch4.89 KBkostyashupenko
overflow-under-glass.png28.74 KBbnjmnm

Issue fork drupal-3163127

Command icon 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

bnjmnm created an issue. See original summary.

kostyashupenko’s picture

Status: Active » Needs review
StatusFileSize
new4.89 KB

Not sure if we have to provide a fix for extrasmall modifier

KondratievaS’s picture

StatusFileSize
new106.5 KB

Tested patch from #2 for mobile and desktop resolutions in Chrome, FF, Safari and IE browsers. Result is OK

OK

KondratievaS’s picture

Status: Needs review » Reviewed & tested by the community
bnjmnm’s picture

Status: Reviewed & tested by the community » Needs work
StatusFileSize
new338.79 KB

This approach changes the widths of the fields so an autocomplete with size="60" would result in a different with than a text field with size="60" . This either needs to be addressed or we'd need design+maintainer approval on making this change.

sd9121’s picture

Assigned: Unassigned » sd9121
sd9121’s picture

Assigned: sd9121 » Unassigned
akshay kashyap’s picture

Please tell the step to reproduces this issue. I have try to reproduces this issue but not able to reproduces.

bnjmnm’s picture

To 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.

boulaffasae’s picture

Status: Needs work » Needs review
StatusFileSize
new2.79 KB

I got the following erros when applying patch #2

error: patch failed: core/themes/claro/css/components/autocomplete-loading.module.css:79
error: core/themes/claro/css/components/autocomplete-loading.module.css: patch does not apply
error: patch failed: core/themes/claro/css/components/autocomplete-loading.module.pcss.css:26
error: core/themes/claro/css/components/autocomplete-loading.module.pcss.css: patch does not apply

Therefore, i couldn't create an interdiff.

I created a new patch based on the #2, i added margin to fix the issue at #5.

ressa’s picture

Status: Needs review » Reviewed & tested by the community
StatusFileSize
new26.79 KB

Great 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.

Tags and text field are the same width.

lauriii’s picture

Status: Reviewed & tested by the community » Needs work
  1. +++ b/core/themes/claro/css/components/autocomplete-loading.module.pcss.css
    @@ -26,7 +26,14 @@
    +  --form-autocomplete-side-padding: calc(2.5625rem - var(--input-border-size));
    +  --form-autocomplete-side-margin: calc(-2.5625rem + var(--input-border-size) + var(--input-padding-horizontal));
    

    Maybe we should make it specific that this is to accommodate the magnifier icon. Maybe something like --form-autocomplete-magnifier-side-padding would work?

  2. +++ b/core/themes/claro/css/components/autocomplete-loading.module.pcss.css
    @@ -26,7 +26,14 @@
    +  margin-right: var(--form-autocomplete-side-margin);
    

    We should have RTL rule for this.

  3. +++ b/core/themes/claro/css/components/autocomplete-loading.module.pcss.css
    @@ -26,7 +26,14 @@
    +  padding-right: var(--form-autocomplete-side-padding);
    +  margin-right: var(--form-autocomplete-side-margin);
    

    We need /* LTR */ comment here because these styles are overridden in the RTL styles.

komalk’s picture

Status: Needs work » Needs review
StatusFileSize
new3.02 KB
new2.93 KB

Worked on #12.

bnjmnm’s picture

Status: Needs review » Needs work
StatusFileSize
new52.05 KB
+++ b/core/themes/claro/css/components/autocomplete-loading.module.pcss.css
@@ -26,7 +26,14 @@
 .js .form-autocomplete {
+  padding-right: var(--form-autocomplete-side-padding);  /* LTR */
+  margin-right: var(--form-autocomplete-side-margin);  /* LTR */
   background-image: url(../../images/icons/868686/magnifier.svg);
   background-repeat: no-repeat;
   background-position: 100% 50%;
@@ -35,6 +42,9 @@

@@ -35,6 +42,9 @@
   display: none;
 }
 .js[dir="rtl"] .form-autocomplete {
+  padding-right: var(--input-padding-horizontal);
+  padding-left: var(--form-autocomplete-side-padding);
+  margin-right: var(--form-autocomplete-side-margin);
   background-image: url(../../images/icons/868686/magnifier-rtl.svg);
   background-position: 0 50%;
 }

RTL 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.

sd9121’s picture

Assigned: Unassigned » sd9121
sd9121’s picture

Assigned: sd9121 » Unassigned
Status: Needs work » Needs review
StatusFileSize
new2.96 KB

Please review this patch.

Thanks!

sd9121’s picture

StatusFileSize
new2.98 KB

I have updated this patch, please review.

Thanks!

bnjmnm’s picture

@sd9121 can you provide interdiffs with your patches? https://www.drupal.org/documentation/git/interdiff

sd9121’s picture

StatusFileSize
new1.23 KB

@bnjmnm, I have uploaded interdiff of patch #16 and #17

Please review.

Thanks!

meena.bisht’s picture

Assigned: Unassigned » meena.bisht
meena.bisht’s picture

StatusFileSize
new74.02 KB

Patch #17 works good to me . Both when we insert from ltr and rtl. Below adding the screenshot.

meena.bisht’s picture

StatusFileSize
new70.76 KB
meena.bisht’s picture

Assigned: meena.bisht » Unassigned
ambuj_gupta’s picture

Assigned: Unassigned » ambuj_gupta
ambuj_gupta’s picture

StatusFileSize
new270.67 KB
new198.36 KB

Test 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.

ambuj_gupta’s picture

Assigned: ambuj_gupta » Unassigned
Status: Needs review » Reviewed & tested by the community
lauriii’s picture

Status: Reviewed & tested by the community » Needs work
  1. +++ b/core/themes/claro/css/components/autocomplete-loading.module.pcss.css
    @@ -26,7 +26,14 @@
    +  --form-autocomplete-magnifier-side-padding: calc(2.5625rem - var(--input-border-size));
    

    Where does 2.5625rem come from? Should this be calculated based on --input-padding-horizontal and the icon size?

  2. +++ b/core/themes/claro/css/components/autocomplete-loading.module.pcss.css
    @@ -26,7 +26,14 @@
    +  --form-autocomplete-magnifier-side-padding: calc(2.5625rem - var(--input-border-size));
    +  --form-autocomplete-side-margin: calc(-2.5625rem + var(--input-border-size) + var(--input-padding-horizontal));
    

    We should rename this using the same pattern. This would become --form-autocomplete-magnifier-side-margin.

sarvjeetsingh’s picture

Status: Needs work » Needs review
StatusFileSize
new3.01 KB
new1.43 KB

I have updated the patch after replacing --form-autocomplete-side-margin to --form-autocomplete-magnifier-side-margin.
I am not sure about the first recommendation, @lauriii, can you provide a lil more information about that?

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

ranjith_kumar_k_u’s picture

StatusFileSize
new244.72 KB
new269.45 KB

I have tested the above patch on 9.2.x dev version ,the patch works fine for claro theme.
Before patch before patch
After Patch after patch.RTBC

ranjith_kumar_k_u’s picture

StatusFileSize
new3 KB

Re-rolled from #28

djsagar’s picture

Status: Needs review » Reviewed & tested by the community
StatusFileSize
new33.46 KB
new30.26 KB

Patch #31 is applied and working on 9.2.x-dev.
I have tested claro theme.

Thanks!

bnjmnm’s picture

Status: Reviewed & tested by the community » Needs work

The 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.

abhisekmazumdar’s picture

StatusFileSize
new3.01 KB
new3.02 KB

Fixed the "custom commands failed" issues. Kindly review

abhisekmazumdar’s picture

Status: Needs work » Needs review
abhisekmazumdar’s picture

StatusFileSize
new3.01 KB
new1.74 KB

Missing one check. Updated the patch.

djsagar’s picture

Status: Needs review » Needs work

Custom commands failed please re-work.

djsagar’s picture

Status: Needs work » Needs review
StatusFileSize
new3.01 KB
new1.78 KB

fixed custom commands failed issue please review.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

sakthivel m’s picture

StatusFileSize
new146.03 KB
new142.45 KB

Applied the patch #38 on 9.3.x and it works fine. Adding screenshots below.

Moved to RTBC

sakthivel m’s picture

Status: Needs review » Reviewed & tested by the community
lauriii’s picture

Status: Reviewed & tested by the community » Needs work

We 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.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

ameymudras’s picture

Status: Needs work » Needs review
StatusFileSize
new3.06 KB

As per the comment #27, calculating the padding using available variables

sonam.chaturvedi’s picture

StatusFileSize
new45.1 KB
new40.55 KB

Verified 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:
bef patch45

After Patch:
after patch45

Moving to RTBC

sonam.chaturvedi’s picture

Status: Needs review » Reviewed & tested by the community

Status: Reviewed & tested by the community » Needs work

The last submitted patch, 45: 3163127-45.patch, failed testing. View results

akshayadhav’s picture

Assigned: Unassigned » akshayadhav
akshayadhav’s picture

Status: Needs work » Needs review
StatusFileSize
new3.06 KB
new742 bytes

Re-uploading the patch with minor fix. Ran code check locally which came out clean.

Manibharathi E R’s picture

StatusFileSize
new100.98 KB
new95.26 KB

Patch #50 tested and Applied successfully on Drupal 9.5.x.

Before patch:
Before-Patch

After Patch:
After-patch

akshayadhav’s picture

Assigned: akshayadhav » Unassigned
bnjmnm’s picture

We're good on screenshots now. A review of the code would be the next step.

nikhilraut’s picture

Assigned: Unassigned » nikhilraut
nikhilraut’s picture

Assigned: nikhilraut » Unassigned
Status: Needs review » Reviewed & tested by the community
StatusFileSize
new86.08 KB
new264.22 KB

Verified 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.

vinaymahale’s picture

StatusFileSize
new9.12 KB

Verified and tested patch#50 on 9.5.x-dev for me. The patch is applied successfully.

Auto complete overflow

vinaymahale’s picture

bnjmnm’s picture

Status: Reviewed & tested by the community » Needs review

@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.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

nod_’s picture

Status: Needs review » Needs work

D10 version needed
At this time we need a D 10.1.x patch or MR for this issue.

sahil.goyal’s picture

StatusFileSize
new3 KB
new2.38 KB

Hi, reroll the patch for the version 10.1.x and attaching the reroll_diff

Ankit.Gupta’s picture

Status: Needs work » Needs review
StatusFileSize
new3.14 KB
nod_’s picture

Status: Needs review » Needs work

The last patch doesn't apply

pradhumanjain2311’s picture

Status: Needs work » Needs review
StatusFileSize
new3.42 KB

As patch #62 is not applied i trued to fix patch #61.
by using yarn build.

deepalij’s picture

StatusFileSize
new57.62 KB
new72.44 KB
new79.12 KB
new72.81 KB

Verified 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

gaurav-mathur’s picture

Applied patch #64 works fine now text in input not overflow the icon on Drupal 10.1.x-dev
Refer to the screenshot

manojkumar_97’s picture

Status: Needs review » Reviewed & tested by the community
bnjmnm’s picture

Status: Reviewed & tested by the community » Needs work
+++ b/core/themes/claro/css/components/autocomplete-loading.module.pcss.css
@@ -24,12 +24,23 @@
+  margin-right: var(--form-autocomplete-magnifier-side-margin); /* LTR */
+  padding-right: var(--form-autocomplete-magnifier-side-padding); /* LTR */

This can be refactored so the RTL portion is not needed: change margin-right to margin-inline-end and change padding-right to padding-inline-end. The RTL additions and the /* LTR */ annotations won't be needed after that.

_utsavsharma’s picture

StatusFileSize
new1.99 KB
new3.4 KB

Made changes as per the comment #68.
Please review.

_utsavsharma’s picture

Status: Needs work » Needs review
bnjmnm’s picture

Status: Needs review » Needs work
+++ b/core/themes/claro/css/components/autocomplete-loading.module.pcss.css
@@ -24,12 +24,23 @@
 .js[dir="rtl"] .form-autocomplete {
+  margin-right: 0;
+  margin-left: var(--form-autocomplete-magnifier-side-margin);
+  padding-right: var(--input-padding-horizontal);
+  padding-left: var(--form-autocomplete-magnifier-side-padding);
   background-image: url(../../images/icons/868686/magnifier-rtl.svg);
   background-position: 0 50%;

Changing 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.

gauravvvv’s picture

StatusFileSize
new3.46 KB
new2.25 KB

I have updated the margin-right with margin-inline-end and margin-left with margin-inline-start and same for padding. Attached interdiff for same. Please review.

gauravvvv’s picture

Status: Needs work » Needs review
nitin shrivastava’s picture

StatusFileSize
new3.46 KB
new1.33 KB

Try to fix ccf error in #72

bnjmnm’s picture

Status: Needs review » Needs work
+++ b/core/themes/claro/css/components/autocomplete-loading.module.css
@@ -31,13 +31,24 @@
 .js[dir="rtl"] .form-autocomplete {
+  margin-inline-start: var(--form-autocomplete-magnifier-side-margin);
+  margin-inline-end: 0;
+  padding-inline-start: var(--form-autocomplete-magnifier-side-padding);
+  padding-inline-end: var(--input-padding-horizontal);
   background-image: url("data:image/svg+xml,%3csvg width='40' height='20' viewBox='0 0 20 20' xmlns='http://www.w3.org/2000/svg'%3e%3cpath d='M12 1c4.54-.173 8.188 4.787 6.687 9.068-1.176 4.384-6.993 6.417-10.637 3.7-.326-.39-.565.276-.846.442l-3.74 3.739-1.413-1.414 4.35-4.35C3.59 8.717 5.25 2.938 9.462 1.475A7.003 7.003 0 0112 1zm0 2c-3.242-.123-5.849 3.42-4.777 6.477.842 3.132 4.994 4.58 7.6 2.65 2.745-1.73 2.9-6.125.285-8.044A5.006 5.006 0 0012 3z' fill='%23868686'/%3e%3c/svg%3e");
   background-position: 0 50%;
 }

The 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-inline and margin-inline. They aren't 1:1 replacements

kristen pol’s picture

Thanks 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

bunty oberoi’s picture

StatusFileSize
new1.66 KB

I have created a Patch for the Autocomplete input text can visibly overflow under the magnifier icon. Please Review

akram khan’s picture

StatusFileSize
new2.35 KB
new1.51 KB

added updated patch and fixed ccf #77

akram khan’s picture

StatusFileSize
new2.28 KB
new1.64 KB

try to fixed CCF #78

bnjmnm’s picture

If 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:

To reproduce this output locally:
* Apply the change as a patch
* Run this command locally: sh ./core/scripts/dev/commit-code-check.sh
OR:
* From the merge request branch
* Run this command locally: sh ./core/scripts/dev/commit-code-check.sh --branch 10.1.x
--- Errors ---
gauravvvv’s picture

Status: Needs work » Needs review
StatusFileSize
new4 KB
new2.85 KB

Updated short hand properties in #74, Attached interdiff for same.

bunty oberoi’s picture

StatusFileSize
new20.21 KB

Hi Gauravvvv,
The patch applied cleanly.
Autocomplete input text is looking fine now Here are the screenshots.

bunty oberoi’s picture

StatusFileSize
new28.04 KB
smustgrave’s picture

Issue summary: View changes
Status: Needs review » Needs work
Issue tags: +Needs Review Queue Initiative, +Needs issue summary update

Removing credit for bad rerolls

This appears to need an issue summary also.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

vinaymahale’s picture

Any more work needs to be done here?

vinaymahale’s picture

chi’s picture

@smustgrave what needs to be updated in the issue summary?

smustgrave’s picture

IS is incomplete, no steps to reproduce, proposed solution, if UI change screenshots are needed.

shweta__sharma’s picture

Issue summary: View changes
Status: Needs work » Needs review
StatusFileSize
new75.29 KB
new265.63 KB
new75.29 KB

Issue summary updated.

smustgrave’s picture

Status: Needs review » Needs work

Still has TBD in the proposed solution.

scott_euser made their first commit to this issue’s fork.

scott_euser’s picture

Issue summary: View changes
Status: Needs work » Needs review
  1. Converted to merge request
  2. Resolved conflicts
  3. Updated issue summary
bnjmnm’s picture

Status: Needs review » Needs work

See MR

scott_euser’s picture

Status: Needs work » Needs review
StatusFileSize
new14.78 KB

Thanks! 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.

Screenshot of the input after dir rtl added to html element

scott_euser’s picture

Does this mean we should move the calc's from
:root {
into the
.js { & .form-autocomplete {
?

scott_euser’s picture

I think yes looking at other pcss files in core, so I have gone ahead and done that.

utkarsh_33’s picture

Issue summary: View changes
StatusFileSize
new56.89 KB
new57.31 KB

Added LTR and RTL views after the changes.

smustgrave’s picture

Status: Needs review » Reviewed & tested by the community
Issue tags: -Needs issue summary update

Removing 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

nod_’s picture

Version: 11.x-dev » 10.3.x-dev
Status: Reviewed & tested by the community » Fixed

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!

  • nod_ committed 42a97ff4 on 10.3.x
    Issue #3163127 by scott_euser, Gauravvvv, sd9121, djsagar,...

  • nod_ committed f9e6633c on 10.4.x
    Issue #3163127 by scott_euser, Gauravvvv, sd9121, djsagar,...

  • nod_ committed 351c0873 on 11.0.x
    Issue #3163127 by scott_euser, Gauravvvv, sd9121, djsagar,...

  • nod_ committed 90f8dd19 on 11.x
    Issue #3163127 by scott_euser, Gauravvvv, sd9121, djsagar,...
nod_’s picture

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.