Details
-
Bug
-
Resolution: Unresolved
-
Trivial
-
None
-
None
Description
0.4.15-dev-3878-gd9f156e is affected
Reproduction steps
- Move the mouse over the clock in the systray and do not wait for its tooltip to appear but instead quickly open the context menu, before the tooltips timer fired
Observed result
context menu opens, but then afterwards still the tooltip nags the user
Expected result
the tooltip never becomes visible. Its timer must be canceled and if it's already shown then it should be hidden explicitly (for thread-safety). It should not disturb the interaction with the context menu. Context menu should have priority for good user experience. I tested that with MS explorer on XPSP3.
I am not sure, whether it is explorers job to cancel that timer if the context-menu was invoked, or whether some deeper code in ros is responsible for that.
It could be tested by testing our explorer on Windows.
If it fails there too, then it's explorers fault.
If it succeeds there, then it's most likely ros Win32SS fault
0.4.15-dev-3878-gd9f156e_nastyTooltip.webm
0.4.15-dev-3878-gd9f156e_nastyTooltip.log (the log is useless, ros logs nothing when it fails like that)
Attachments
Issue Links
- blocks
-
CORE-11444 Mouse hover on clock doesn't show date hint
- Resolved