| Summary: | Full representation popups of panel applets don't receive focus when opened by keyboard shortcut | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Rohan Garg <rohan> |
| Component: | general | Assignee: | Sebastian Kügler <sebas> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | aleixpol, bhush94, gladhorn, kde, me, mgraesslin, mklapetek, notmart, rohan |
| Priority: | NOR | ||
| Version: | master | ||
| Target Milestone: | 1.0 | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Rohan Garg
2014-05-29 15:27:15 UTC
Seems the dialog window just isn't getting focus at all. can't reproduce here, the focus seems correctly assigned to kickoff when started with alt+f1 both with kwin 4 and 5 Just tested this on KWin5, the focus is not getting set when it launched via a shortcut, it is set when manually clicking on the plasmoid. may it depend from focus policy or focus stealing prevention? that's a month old? Is that still valid, I had a fix in kglobalacceld which should fix it. buh, couldn't reproduce back then, can't reproduce now :p I can still reproduce it on neon as of today. Didn't try with kicker, but IM and kickoff work just fine. Click, start typing, works. Can you verify with other applets? Aha, you clicked, I'm triggering it with a keyboard shortcut. I can't reproduce it on kickoff though. ok, just assigned a keyboard shortcut to kickoff and it works there. What's your focus policy? Click to Focus , however as mentioned, kickoff works perfectly, but kicker does not. I think it's just somewhere else the focus. If I use a keyboard shortcut to trigger the ktp-contactlist plasmoid. I can't type, but then if I press tab, the focus goes to the input box, so the focus already was somewhere within the window. I think the focus should be in the view by default, though. *** Bug 337268 has been marked as a duplicate of this bug. *** Seems fixed now (Frederick Gladhorn made some changes recently) please reopen if still broken with latest master Yes, the problem was actually calling forceActiveFocus setting the focus unconditionally on the root item. Usually that's not what one wants (some sub item should have the focus and had focus: true, but forceActiveFocus overrides that happily). so the lesson is to use force with care ;) |