User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040514 Build Identifier: When rolled up or "shaded", windows do not receive keystrokes. Unrolling the window and *not* moving the mouse cursor will allow keystrokes to be sent to the focused app. Reproducible: Always Steps to Reproduce: Example1: 1. Open firefox and visit a website. 2. Shade/roll-up window. 3. Press ctrl-W or ctrl-Q. Example2: 1. Open terminal window. 2. Shade/roll-up window. 3. Press ctrl-D. Actual Results: Nothing happens. Expected Results: Firefox should quit or at least that window should close. Terminal window should disappear. $ xfwm4 --version This is xfwm4 version 4.3.99.1 (revision 23062) for Xfce 4.3.99.1 Released under the terms of the GNU General Public License. Compiled against GTK+-2.8.16, using GTK+-2.8.16. Build configuration and supported features: - Startup notification support: No - Render support: No - Xrandr support: No - Embedded compositor: No - KDE systray proxy (deprecated): No
Forgot to mention that this bug is present in both the latest SVN checked out as of yesterday and also 4.4rc1.
If you mean that, when shaded, the window doesn't receive keyboard events, well, it's normal as the client window is unmapped. Until 4.4 beta2 or RC1, windows where receiving keyboard events because the client windows was still mapped but kept not visible, but some ppl complained about that, see bug #2168 for more details. If you mean that keyboard shortcuts doesn't work once the window is shaded, then it's a dup of bug #2291. Either way, it's fixed or not a bug.
Reopening bug as a feature request. I would like to regain the ability to send keystrokes to shaded applications. Perhaps an option placed in WM tweaks?
No, it's not optional, sorry.
Just for clarification, it cannot optional because it's really different ways of doing the shading and it wouldn't make sense to keep the two implementations concurrently... It's less "hacky" now, and more in line with other window managers, so I won't revert to the previous behavior. Not to mention that, as already stated, some apps (arguably buggy maybe?) rely on the client window to be unmapped when shaded.