Skip to content

clutter/input-pointer-a11y: Fix dwell timeout start after moving pointer

Jonas Dreßler requested to merge verdre/mutter:pointer-a11y-fixes into master

Sometimes the dwell timeout doesn't start again after quickly moving the pointer. That happens if should_stop_dwell returns TRUE for the last motion event we receive: It will stop the current timeout, but not start a new one until we receive another event where the moved distance is smaller than the threshold.

To fix this, always call should_start_dwell and start_dwell_timeout instead of using an else-block, this makes sure we start a new dwell timeout still during the same motion event that stopped the old one.

@ofourdan I'm actually not sure if this is a bug or if it was intended like this?

Merge request reports