- Issue created by @javi-er
- First commit to issue fork.
- Merge request !5643Issue #3405576: Fix horizontal scroll on tabledrag → (Closed) created by penyaskito
- Status changed to Needs review
over 1 year ago 4:41pm 1 December 2023 - 🇪🇸Spain penyaskito Seville 💃, Spain 🇪🇸, UTC+2 🇪🇺
Created a merge request with a solution that worked for us. Javi-er thinks this might be a broader issue and not only affecting tabledrag.
- Status changed to Needs work
over 1 year ago 9:43pm 3 December 2023 - 🇺🇸United States smustgrave
as UI issue could a screenshot of the issue be added to the issue summary.
- Status changed to Needs review
over 1 year ago 9:41am 4 December 2023 - First commit to issue fork.
- 🇮🇳India ankithashetty Karnataka, India
+ RTBC.
Tested the MR and it fixed the reported issue. Also IS updated with required SS.Followed the same steps shared in IS to test it.
After applying the MR:
- 🇷🇺Russia kostyashupenko Omsk
First of all, issue target version is
10.1.x
, but MR was created against11.x
branch. So switching issue version to11.x
. However bug exist in10.x
and11.x
and since it's a bug report, we can merge it directly in10.x
. I checked - the latest diff in MR can be applied in10.x
with no problem.About original problem - input type text have
size
attribute, which potentially can be different, but core hassize="60"
by default. The width of container of input element is more than thissize
, that's why when not enough viewport width - input element goes out of viewport. So we need to add 100% width to the input element itself (because currently it doesn't have it, but should have for specific case in table). Also, when we are using autocomplete input fields - those fields have extra wrapper<div class="claro-autocomplete">
, which hasdisplay: inline-block
CSS styles. Which means if we set lowsize
on the input element, likesize="10"
, the entire width of input field will be too narrow (but should be 100%). The fix provided in #4 🐛 Table drag elements create horizontal scroll on mobile Needs review is added in wrong place. We already have same kind of fix in another place intable.pcss.css
file, which works ok for input fields which are not autocomplete input fields. SO i just added one more CSS line to wrap autocomplete cases.This is result:
I think this issue can be easily reviewed & merged
- Status changed to Needs work
over 1 year ago 10:08am 4 December 2023 - 🇮🇳India ankithashetty Karnataka, India
Update:
The test results shared in #8 are w.r.t to MR in #3. => Works as per expectation.Tried the #7 MR, but it didn't fix the scroll issue for me.
Changing back to 'Needs work' status.
@kostyashupenko Could you please check again? Hope you have opened the main navigation during the fix while testing.
Thanks! - Status changed to Needs review
over 1 year ago 12:24pm 4 December 2023 - 🇷🇺Russia kostyashupenko Omsk
I found 2 issues:
1. I forgot to put one more CSS line (now fixed)
2. on your video you have enabled aggregration (did you clear cache?). Even with previous commit you should havewidth: 100%
on the.claro-autocomplete
CSS selector, but i don't see it in your video.Anyway let's re-test again, now works even with opened navigation. Sorry )
- Status changed to Needs work
over 1 year ago 1:17pm 4 December 2023 - 🇮🇳India ankithashetty Karnataka, India
Thanks for the update!
Tested again with the same steps, here are my observations:
* After applying the latest change, disabled aggregation and cleared cache (multiple times)case #1. The fix works when we have a single autocomplete field
case #2. If we add another term/item, then we still see the scrolling issue. (Fix in #3 worked in both the scenarios)
Need to check on case 2.
Thanks! - Status changed to Needs review
over 1 year ago 4:27am 5 December 2023 Hi @kostyashupenko
I have tested MR 5643 on Drupal 11 and it's working fine.
The scrolling issue has been fixed when open the navigation menu for both cases.
Attached small recording.
Thanks- Status changed to RTBC
over 1 year ago 5:36am 5 December 2023 - 🇮🇳India ankithashetty Karnataka, India
Thanks again @kostyashupenko!
+1 to RTBC
Steps to reproduce (shared in IS)
1- Create an entity reference field on a content type.
2- Choose 2 items or more on the "number of values" setting.
3- Visit the form page and open it at 712px width, open the main navigation.Tested:
case #1. The fix works when we have a single autocomplete field.
case #2.Also works when we add another item.Thanks!
- Status changed to Fixed
over 1 year ago 7:41am 8 December 2023 Automatically closed - issue fixed for 2 weeks with no activity.