Currently the icon select widget is broken with the new experimental theme Claro.
The icon svg is placed in a weird place.
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | icon_select-icon_select_widget_broken_with_claro-3173774-13.patch | 4.18 KB | onfire84 |
| #8 | after.png | 15.92 KB | ayalon |
| #8 | before.png | 13.38 KB | ayalon |
| #6 | 3173774-6-claro-styles.patch | 1.1 KB | grahl |
| claro_icon_widget.png | 20.5 KB | heikkiy |
Issue fork icon_select-3173774
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
Comment #2
heikkiy commentedSeems like following styles for Claro seem to fix most of the issues:
Comment #3
ayalon commentedPlease provide a patch, then I can fix the issue upstream.
Comment #4
ayalon commentedComment #5
grahlWe've been using the following in our project (might be too Claro-specific in terms of formatting though).
Comment #6
grahlUpdated the paths.
Comment #7
kleiton_rodrigues commentedI am working on revising this patch.
Comment #8
ayalon commentedUnfortunatly, the patch breaks the styles for the Seven (default) theme.
I cannot merge it without breaking a lot of sites.
Is there a possibility to add some claro specific classes? Is there a wrapper class maybe?
Before:

After:

Comment #9
ayalon commentedComment #10
kleiton_rodrigues commentedComment #12
onfire84 commentedAs of #8 i see, that we need here a switch to apply the changes only for claro theme.
So i applied a custom css class to the detail wrapper of the forms element, to determine the admin theme context. The class is
admin-theme-[THEMENAME]This way we can add css for different admin themes separately.
Also i added the css from #6 wrapped in the 'admin-theme-claro' theme class, so it only will be applied for claro.
All those changes can be found in the issue fork 'icon_select-3173774' in branch '3173774-claro-css-fixes'
Comment #13
onfire84 commentedAdded a patch containing the same as the merge request.
Comment #15
ayalon commentedI like your proposal. Will be committed.
Comment #17
ayalon commentedComment #18
ayalon commentedComment #19
dan_metille commented@ayalon Sorry to write on a closed issue, but it seems to me that the patch #13 never really was committed. At least the issue is still happening with the last releases (2.0.2, released on 23 June 2022, before you closed this issue). And also the patch is applying without complain, which also means that it is not part of the current release code.