unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, 61337@debbugs.gnu.org
Subject: bug#61337: 29.0.60; Setting frame-title-format makes Emacs to steal focus
Date: Thu, 09 Feb 2023 17:17:40 +0100	[thread overview]
Message-ID: <87cz6ivmmz.fsf@telefonica.net> (raw)
In-Reply-To: <83o7q2ltsj.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 09 Feb 2023 17:53:17 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> > Oscar meant that KWin focused the frame without changing the position of
>> > Emacs in the window stack.  That isn't the bug which was reported, Emacs
>> > being focused was.
>> 
>> Right. The part about the z-order not changing just makes the problem
>> worse.
>> 
>> For instance: let's suppose that Emacs window is hidden by some other
>> application's window, (Konsole for instance) that also has the focus.
>> When I switch desktops Emacs will steal the focus, but otherwise the
>> screen's appearence will not change, which makes me think that Konsole
>> still has the focus, then I start typing but the input go to Emacs, and
>> this too often causes a mess.
>> 
>> Same thing could happen even when Emacs' window is visible, of course.
>> After all, the user does not expect that switching desktops changes the
>> focus to certain application's window.
>
> You mean, you rely on the focus not to change while Emacs's desktop is
> not shown?  But if some idle timer causes Emacs to raise a frame, you
> will also see Emacs with focus when you switch desktops, right?
>
> I'm not sure I understand the basis for this expectation.  I'd
> certainly not even remember in which state I left the applications
> before switching away, and will look first when I switch back.

Sure, but on this case you will see that Konsole's window is covering
Emacs' (if Emacs' window is visible at all), so you assume that Konsole
has the focus. For avoiding that you must take care of looking at some
place that indicates which window has or has not focus (usually the
window's title bar) noticing that Konsole has no focus, and perform an
action to either give focus to Konsole or bring Emacs' window to the
front.

> because applications can request focus for any number of reasons.
>
> So I'm surprised that the fact that Emacs gets focus without your
> knowing is regarded as a problem at all.

Focus stealing is widely regarded as a very rude action. Imagine you are
typing on some application and suddenly some other application pops out
and starts receiving your keypresses. That's a disaster, even a gross
security issue. Modern desktop environments implement a notification
system to make possible for an application to show information or
request user attention without stealing the focus, so nowadays there is
no good reason for getting focus without the user's request. AFAIR in
Wayland it is simply not possible for an application to forcibly get the
focus.

Certainly, just switching destktops is not one good reason for stealing
the focus.





  reply	other threads:[~2023-02-09 16:17 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-07  5:07 bug#61337: 29.0.60; Setting frame-title-format makes Emacs to steal focus Oscar Fuentes
2023-02-07 14:15 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-07 15:29   ` Óscar Fuentes
2023-02-08  1:16     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08  2:45       ` Óscar Fuentes
2023-02-08  3:59         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08  4:15           ` Óscar Fuentes
2023-02-08  4:48             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-08 15:24               ` Óscar Fuentes
2023-02-09  2:20                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09  3:17                   ` Óscar Fuentes
2023-02-09  8:15                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09  8:43                       ` Eli Zaretskii
2023-02-09 10:23                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 11:22                           ` Eli Zaretskii
2023-02-09 14:16                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-09 15:32                               ` Óscar Fuentes
2023-02-09 15:53                                 ` Eli Zaretskii
2023-02-09 16:17                                   ` Óscar Fuentes [this message]
2023-02-09 16:50                                     ` Eli Zaretskii
2023-02-10  2:15                                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-10  5:07                                         ` Óscar Fuentes
2023-02-10  7:15                                         ` Eli Zaretskii
2023-02-10  1:59                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-10  4:56                                   ` Óscar Fuentes
2023-02-13 16:02                                   ` Óscar Fuentes
2023-02-14  2:02                                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87cz6ivmmz.fsf@telefonica.net \
    --to=ofv@wanadoo.es \
    --cc=61337@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).