Bug 395436 - Menu Taskbar on the Left edge executes the auto-hide animation twice if mouse is kept touching the edge.
Summary: Menu Taskbar on the Left edge executes the auto-hide animation twice if mouse...
Status: RESOLVED DUPLICATE of bug 393005
Alias: None
Product: plasmashell
Classification: Plasma
Component: Panel (show other bugs)
Version: 5.12.5
Platform: Manjaro Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-15 15:50 UTC by Nico
Modified: 2018-06-15 22:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nico 2018-06-15 15:50:10 UTC
As mentioned in the tile, if taskbar is moved to the left side of the screen and auto-hide is on, the animation of "unhide" is executed twice if the mouse pointer is kept touching the left edge

Running:
* KDE Plasma Version: 5.12.5
* KDE Frameworks version: 5.46.0
* Qt Version: 5.11
* Kernel Version 4.14.40-1-MANJARO
* Two monitors, side by side, with taskbar on the left monitor

How to reproduce:
1) Move taskbar to the left of the screen and enable the auto-hide option
2) Let it hide
3) Move the mouse to the left edge of the screen
>>>> The taskbar will come up once,
4) Keep the mouse touching the right edge of the screen for a little longer (half a second)
>>>> If the mouse is still touching the edge of the screen for another half a second the taskbar flashes (disappears and comes up from hidden again)

Thus it effectively executes the animation twice.
Note that if you touch the edge and remove the mouse from there, the animation is only executed once.

Thanks
Comment 1 Patrick Silva 2018-06-15 21:12:01 UTC
bug 393005 seems related/duplicate.
Comment 2 Nico 2018-06-15 21:53:55 UTC
Indeed, it seems like the same bug. First time reporting a bug here. How to mark as duplicate without marking as "resolved"?
Comment 3 Patrick Silva 2018-06-15 21:56:49 UTC

*** This bug has been marked as a duplicate of bug 393005 ***
Comment 4 Nico 2018-06-15 22:02:58 UTC
Thanks!