Bug 457788 - Hiding an item from the tray while its tooltip is visible results in the tooltip relocating itself to the upper left corner of the display instead of getting removed as well
Summary: Hiding an item from the tray while its tooltip is visible results in the tool...
Status: RESOLVED FIXED
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Tray widget (show other bugs)
Version: 5.25.4
Platform: Arch Linux Linux
: NOR minor
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-12 08:36 UTC by Alexander M.
Modified: 2024-08-23 21:26 UTC (History)
3 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander M. 2022-08-12 08:36:08 UTC
SUMMARY
If a tray item (in my case the "Lock Key Status" item) is visible in the tray (in my case by enabling Caps Lock) and gets removed (in my case by disabling Caps Lock) while the mouse is hovering over it to show its tooltip, then, instead of the tooltip getting destroyed along with the no longer visible tray item, it is instead relocated to the top left corner of the display (presumably because it no longer has an "anchor" for itself to position properly).


STEPS TO REPRODUCE
1. Enable "Lock Key Status" tray applet
2. Turn on Caps Lock
3. Hover your mouse over the applet so the tooltip is displayed
4. Without moving the mouse, press the Caps Lock key to disable it

OBSERVED RESULT
The applet's tooltip is relocated to the top left corner of the display

EXPECTED RESULT
The tooltip should be bound to its parent and disappear immediately when the parent is no longer active

SOFTWARE/OS VERSIONS
KDE Plasma Version: 5.25.4
KDE Frameworks Version: 5.96
Qt Version: 5.15.5+kde
Comment 1 Nate Graham 2022-08-12 20:20:13 UTC
Hah, can reproduce.
Comment 2 Nate Graham 2024-08-23 21:26:32 UTC
Cannot reproduce anymore in current git master, which will soon before Plasma 6.2. Looks like it got fixed along the way. Possibly by the Qt 6 adoption, possibly by something else.