AllBugsFeaturesChangelogSearchNew post
Sign in with Fluxer
Bugs

Edit history

Earlier versions of Reduce Motion waits during animations instead of skipping them(?), newest first.

Current version | Edited by wooper
Changes
Observed behaviourRemoved: When Reduce Motion is enabled, several menu items, when clicked, seem to not do anything until further notice until said menu pops in, instead of immediately transitioning to that menu. Disabling Reduce Motions instead shows an animation in the time in which the client appears frozen (or at least this is what I feel like is happening). This, to me, feels unresponsive.Added: When Reduce Motion is enabled, several menu items, when clicked, seem to not do anything until further notice until said menu pops in, instead of immediately transitioning to that menu. Disabling Reduce Motions instead shows an animation in the time in which the client appears frozen (or at least this is what I feel like is happening). This (with Reduce Motion enabled), to me, feels unresponsive.Tested on 2 Arch Linux devices - native package, flatpak and AppImage.
Show

Reduce Motion waits during animations instead of skipping them(?)

Observed behaviour

When Reduce Motion is enabled, several menu items, when clicked, seem to not do anything until further notice until said menu pops in, instead of immediately transitioning to that menu. Disabling Reduce Motions instead shows an animation in the time in which the client appears frozen (or at least this is what I feel like is happening). This (with Reduce Motion enabled), to me, feels unresponsive. Tested on 2 Arch Linux devices - native package, flatpak and AppImage.

Reproduction steps

With Reduce Motion off, click the Gear Icon to get to the Settings Menu (or hit Ctrl+,). Observe the animation. Now turn Reduce Motion on. Again, go to the Settings. Observe the animation. Compare the differences in perceived responsiveness.

Build information

Canary Desktop 2026.1009.45608, Web 2026.1009.142425, Linux 7.2.8-zen1-2-zen (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US

Platform

Linux

Edited by wooper
Changes
Observed behaviourRemoved: When Reduce Motion is enabled, several menu items, when clicked, seem to not do anything until further notice until said menu pops in, instead of immediately transition to that menu. Disabling Reduce Motions instead shows an animation in the time in which the client appears frozen (or at least this is what I feel like is happening). This, to me, feels unresponsive.Added: When Reduce Motion is enabled, several menu items, when clicked, seem to not do anything until further notice until said menu pops in, instead of immediately transitioning to that menu. Disabling Reduce Motions instead shows an animation in the time in which the client appears frozen (or at least this is what I feel like is happening). This, to me, feels unresponsive.Tested on 2 Arch Linux devices - native package, flatpak and AppImage.
Show

Reduce Motion waits during animations instead of skipping them(?)

Observed behaviour

When Reduce Motion is enabled, several menu items, when clicked, seem to not do anything until further notice until said menu pops in, instead of immediately transitioning to that menu. Disabling Reduce Motions instead shows an animation in the time in which the client appears frozen (or at least this is what I feel like is happening). This, to me, feels unresponsive. Tested on 2 Arch Linux devices - native package, flatpak and AppImage.

Reproduction steps

With Reduce Motion off, click the Gear Icon to get to the Settings Menu (or hit Ctrl+,). Observe the animation. Now turn Reduce Motion on. Again, go to the Settings. Observe the animation. Compare the differences in perceived responsiveness.

Build information

Canary Desktop 2026.1009.45608, Web 2026.1009.142425, Linux 7.2.8-zen1-2-zen (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US

Platform

Linux

Original by wooper
Show

Reduce Motion waits during animations instead of skipping them(?)

Observed behaviour

When Reduce Motion is enabled, several menu items, when clicked, seem to not do anything until further notice until said menu pops in, instead of immediately transition to that menu. Disabling Reduce Motions instead shows an animation in the time in which the client appears frozen (or at least this is what I feel like is happening). This, to me, feels unresponsive. Tested on 2 Arch Linux devices - native package, flatpak and AppImage.

Reproduction steps

With Reduce Motion off, click the Gear Icon to get to the Settings Menu (or hit Ctrl+,). Observe the animation. Now turn Reduce Motion on. Again, go to the Settings. Observe the animation. Compare the differences in perceived responsiveness.

Build information

Canary Desktop 2026.1009.45608, Web 2026.1009.142425, Linux 7.2.8-zen1-2-zen (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US

Platform

Linux