[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 187718] Focus screwed up after closing emacsclient window (with
From:       Alain Knaff <kde () kde ! lka ! org ! lu>
Date:       2010-06-02 14:30:18
Message-ID: 20100602143018.D857C4351A () immanuel ! kde ! org
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=187718





--- Comment #7 from Alain Knaff <kde kde lka org lu>  2010-06-02 16:30:04 ---
> the extreme focus protection will cause windows to not raise or get focus on
> mapping.

Yes, I noticed that. Is this by intent (in order to avoid windows from getting
focus by popping up under the mouse pointer?) or is it a side effect of
something else?

> the VD
> should maybe just not switched on window maps. this may be bug or intention.
> don't know.

If it is intentional, let me point out that this would indeed be annoying...
(but fortunately rare)

> is that if(f) a client uses the
> forcefull way to gain focus, there's no way to figure who called the 
> activation and whether it's really a WM tool or not. I do not even see any 
> relation to the focus protection level.

I get the impression that this changes every time that I bring up a new element
to the discussion. Maybe the easiest would be to enumerate the (common) ways
how an application could force focus, and say for each of these ways:

1. Whether it is affected by focus protection level (and which level)
2. Whether it is possible to find out whether it was a WM tool or not.

Obviously some WM tool manage to set focus even when focus protection level is
set to high. This raises 2 remarks:
1. If a high focus protection level doesn't interfere with WM tools, why did
you bring up WM tools in the first place? ( in bug #240332, comment 9 )
2. If on the other hand the WM cannot tell which request came from a WM tool,
and which one came from an app, couldn't a malicious or careless app also use
the same APIs that WMs use and that still "work" on high focus protection
levels? And how likely is it that a careless or clueless app would do this
accidentally (we're speaking about respectable mail programs and editors here
after all, not about bonzai-buddy-like trojans...)?

Sorry, all this is way confusing, and somehow I get the impression that it is
full of contradictions...

I just hope that all this is not a case of "Windows has a similarly annoying
quirk, and we have to be like Windows if we want to win the desktop" (which
would be weird, as windows doesn't even normally have virtual desktops, but you
never know...)

> the window list widget would have to use the forcefull activation. that's
> matter on whether it considers itself as a WM on one level with a pager or 
> not.

... and is there any mechanism in place (or even possible) to make sure that
such activation is *only* used by WM tools (and not by apps such as
thunderbird...). Or is it all just on a voluntary basis?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
[prev in list] [next in list] [prev in thread] [next in thread]