🇷🇸Serbia @alex.87

I can't reproduce this issue following the Testing steps.

I can't reproduce this either, can you please add screenshots and maybe update the Testing steps with additional details?

So in https://www.drupal.org/project/drupal/issues/3291549 📌 Refactor Claro's "node form" layout to not use floats Fixed we changed the layout-node-form to use `grid` instead of `float`, and a combination of a grid and long select is causing these issues, still looking for the best solution, but if I use flex instead of the grid all of the issues with nested elements are resolved.

Kanchan Bhogade please use the testing steps from the IS. Create a new taxonomy, or edit the existing one, create a long term, and add it as a select list to the node, do not use the autocomplete.

Please ignore the !5582 and test the !6291. I can't close the !5582 because I was not the original creator of the MR.

Added Before/After screenshot. Updated summary to match the latest code that is different after pulling the latest 11.x.

Created MR against 11.x.

Not sure how it got lost, but I took it back from the revision.

alex.87 → created an issue.

@jurgenhaas is this 10.2.x issue or 11.x?

alex.87 → made their first commit to this issue’s fork.

Personally, I don't think this is an issue, it is just how the select list works across the browsers.

But in case I'm wrong I submitted a new MR with a small change. I changed `34.3rem` to 100% as the first one is not working well with the small devices.

alex.87 → made their first commit to this issue’s fork.