https://bugs.kde.org/show_bug.cgi?id=363892
--- Comment #2 from Martin Gräßlin <[email protected]> --- I did some testing including running with openbox and can confirm that with openbox the behavior is different. But I'm not convinced that we have a KWin bug here, due to the following: One of the things I observed is that Qt doesn't update the state correctly even if the events are reported correctly. E.g: TestCase(16540)/(default) unknown: focusIn QSlider(0x197dd40, name = "horizontalSlider") TestCase(16540)/(default) unknown: focusIn QWindow(0x1970750) TestCase(16540)/(default) unknown: focusOut QSlider(0x197dd40, name = "horizontalSlider") In that state the horizontalSlider is rendered in active state although it's clearly not active given the reported events. On very first activation that works correctly. My test case was: 1. run the test applications from the linked bug report 2. focus on the embedded QWindow - observe slider becomes inactive 3. focus on the slider - observe slider becomes active 4. focus another window - observe slider becomes inactive 5. focus on the embedded window - observe slider becomes active The events in case 5 are the ones printed above: TestCase(16561)/(default) unknown: focusIn QSlider(0xf5eda0, name = "horizontalSlider") TestCase(16561)/(default) unknown: focusIn QWindow(0xf634b0) TestCase(16561)/(default) unknown: focusOut QSlider(0xf5eda0, name = "horizontalSlider") Qt clearly does not handle that case correctly. I'm not convinced that this is a KWin bug. -- You are receiving this mail because: You are watching all bug changes.
