Iain Lane e6dec7a9dd volume: Ignore slider changes we initiated ourselves ... Commit 21e14bd46f fixed this for the brightness slider, but we have the same problem for volume too. When the volume is muted - for example in Settings or via a media key, we update the slider to '0' to indicate this visually. But we also actually invoke the slider's callback to *set* the volume to zero. That means that the previous level is overwritten so it can't be restored when unmuting. The fix is the same - when we update the slider internally ourselves, don't call the signal handler. https://gitlab.gnome.org/GNOME/gnome-shell/issues/1557		2019-09-05 11:30:33 +01:00
..
extensionPrefs	extensionPrefs: Request correct GDK/GTK versions	2019-08-21 19:43:33 +02:00
gdm	js: Use Clutter transitions for adjustment changes	2019-08-07 18:40:49 +02:00
misc	windowManager: Handle starting/stopping of X11 services	2019-09-05 07:42:46 +00:00
perf	perf: Shut up another eslint error	2019-07-24 00:28:45 +02:00
portalHelper	cleanup: Mark globals used from other modules as exported	2019-07-24 00:28:45 +02:00
ui	volume: Ignore slider changes we initiated ourselves	2019-09-05 11:30:33 +01:00
js-resources.gresource.xml	accessibility: Add pointer accessibility support	2019-06-06 09:13:29 +02:00
meson.build	build: Use dedicated resources for helper programs	2018-08-14 17:28:04 +00:00
portal-resources.gresource.xml	build: Include params.js in portal-helper gresources	2018-10-23 15:38:31 +00:00
prefs-resources.gresource.xml	build: Use dedicated resources for helper programs	2018-08-14 17:28:04 +00:00