Closed (fixed)
Project:
Select 2
Version:
8.x-1.x-dev
Component:
Field widgets
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
19 Feb 2020 at 12:26 UTC
Updated:
17 Jan 2022 at 06:42 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #2
sasanikolic commentedHere is the patch with the proposed fix and the screenshot of how that looks. Note that we need a more specific selector than just
.select2-container--sevenas in that case the select2 will overlap the modal itself.Comment #3
mbovan commentedTested with Seven and Claro themes.
It works well with the Seven theme, but the same problem still appears with Claro theme.
I think we should have a fix for Claro too.
Comment #4
sasanikolic commentedSeems like select2 supports only seven theme. There are only select2.seven.css and select2.seven-overrides.css in the module which get loaded only for the seven theme. Also, all selectors are explicitly set to .select2-container--seven.
There is a separate issue for Claro integration: https://www.drupal.org/project/select2/issues/3100219. I think all custom css styles will be ported there.
Comment #5
mbovan commentedI commented in #3100219: Add a claro theme to connect these two issues.
That said (#4), this should be ready IMHO.
Comment #6
berdirLooks like this needs a reroll.
Comment #7
mrinalini9 commentedRerolled patch for 8.x-1.x, please review.
Comment #8
chr.fritschTrigger the tests https://github.com/thunder/select2/pull/95
Comment #10
chr.fritschDone, thank you
Comment #12
aludescher commentedThe issue is still there with latest dev.
Some issues I came accross:
.ui-widget-overlay ~ & { z-index: 1260; }is not enough. We could use '.ui-dialog ~ &' instead.It's not clear to me why only the seven, claro and gin themes should contain this fix? Can't we add it to a generic css file and override it with a theme specific one when it's the case?
In addition to the above the attached patch also removes duplicate code from select2.seven.scss:
Comment #13
berdirI would strongly suggest that you create a new issue. I only saw it due to a mail notification, it will almost certainly get overlooked in here.
Comment #14
aludescher commentedThanks @Berdir, issue created: https://www.drupal.org/project/select2/issues/3258855