View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0016866 | MMW 5 | Main Panel | public | 2020-08-03 16:37 | 2021-01-21 01:47 |
Reporter | lowlander | Assigned To | |||
Priority | urgent | Severity | crash | Reproducibility | random |
Status | closed | Resolution | duplicate | ||
Product Version | 5.0 | ||||
Target Version | 5.0.1 | Fixed in Version | 5.0 | ||
Summary | 0016866: MediaMonkey takes keyboard input while not the active window | ||||
Description | I've not noticed this before and it happened after MediaMonkey had been open a while. While working in Firefox, MediaMonkey seemed to keep reacting to keyboard input. In video it shows MediaMonkey moving around the tree while not the active window. | ||||
Tags | No tags attached. | ||||
Fixed in build | 2265 | ||||
duplicate of | 0016130 | closed | petr | Plackback: Spacebar causes focus to switch to MediaMonkey on track transitions |
related to | 0016787 | closed | Ludek | Media Tree Node selection changes, possibly due to scanning |
related to | 0016991 | closed | petr | MediaMonkey steals focus |
related to | 0017414 | closed | petr | MediaMonkey context menus steal focus |
related to | 0017422 | closed | petr | MM steals focus soon after track transitions (regression 2296?) |
|
Video shows 0:55 (and end of log) after using Backspace that Tree starts moving around: https://1drv.ms/u/s!AjRcJhPd0elwgfhBPn3xoPpvk3PfPw?e=TCOQaF |
|
It is curious, but on the video it is really clearly seen that MM takes the keaboard input even when the window is not foreground. It expands/collapses tree nodes when using right/left arrows etc. We are unable to replicate (tested by Ludek & Michal), but to me it looks like a bug in the Chromium engine (that could be potentionally fixed in newer version) as it reacts on 'keydown' events in DOM. Or maybe the FireFox uses a same type of events and somehow redirects it to MM window? @LowLander: Have you found a consistent steps to replicate so that we could test whether Chromium update would fix this or find a clue? |
|
No, this is a rare thing to happen and don't know how to force this (reproduce) to happen. |
|
I've been able to replicate a variant of this issue documented with log at 0016130. The key in that case was: 1) MM must be obscured by another app 2) MM must be playing music 3) User must type the SPACEBAR in the app that is obscuring MM at the time that playback transitions from one track to another. |
|
Seeing that 0016130 was fixed in 2265, so I suppose that this issue is also resolved in 2265. Please test 2265 once is available |
|
Verified 2265 Unable to replicate, background playback or properties edit do not take keyboard actions. Test note: OPen properties and click on Comment to edit -> Switch to other apps like firefox, Notepad++, ... and type. No characters are added to MM in background |