059af4c4cd
There are two ways for applications to provide a high contrast icon:
1. install an icon into the HighContrast theme
2. install a symbolic icon into the default hicolor theme
The latter is preferred nowadays, and implemented in the high-contrast
CSS variant by enforcing the symbolic icon style.
However together with the way we currently enable/disable high-contrast,
this can lead to the following race:
1. the GTK theme is changed from HighContrast
2. we reload the default stylesheet
3. the icon style changes to "regular", so we request a
new icon from the HighContrast icon theme
4. the icon theme is changed from HighContrast
5. we evict existing icons from the cache
6. we reload icons for the new icon theme; however as we
find a pending request (from 3), we re-use it
7. the request from 3 finishes, and we end up with a
wrong icon in the cache
The simplest fix is to change the icon theme before the GTK theme: Unlike the
theme name, the icon style is encoded in the cache key, so we won't re-use
an old (and incorrect) request in that case.
https://gitlab.gnome.org/GNOME/gnome-shell/issues/2414
|
||
|---|---|---|
| .. | ||
| accessibility.js | ||
| bluetooth.js | ||
| brightness.js | ||
| dwellClick.js | ||
| keyboard.js | ||
| location.js | ||
| network.js | ||
| nightLight.js | ||
| power.js | ||
| remoteAccess.js | ||
| rfkill.js | ||
| screencast.js | ||
| system.js | ||
| thunderbolt.js | ||
| volume.js | ||