unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: 40639@debbugs.gnu.org
Cc: alexanderm@web.de
Subject: bug#40639: 26.3; Child frame border color not rendered when child frame has no minibuffer
Date: Sat, 18 Apr 2020 10:51:45 +0200	[thread overview]
Message-ID: <c807be9f-8e02-f273-4c89-44b41f36cede@gmx.at> (raw)
In-Reply-To: <e00c430e-888c-1d7d-0bc3-1cee522adeec@gmx.at>

tags 40639 fixed
close 40639 28.1
quit

 > Digging into this a bit further I found that
 > calling gui_consider_frame_title for child frames fixes it.

Hopefully fixed now on master by calling gui_consider_frame_title for
child frames too.

IMHO this is a bug when refreshing the face cache.  We postpone that for
a new frame until we call gui_consider_frame_title for that frame.
Until then, any earlier attempts to free realized faces are inhibited by
inhibit_free_realized_faces.  It's easy to see the effect with Emacs'
native tooltip frames by evaluating with emacs -Q

(progn
   (setq x-gtk-use-system-tooltips nil)
   (set-face-background 'internal-border "red"))

and moving the mouse to some text on the mode line.  The red border will
show up only after I clicked at least once into the containing frame.

If the bug affects the internal border only, it's minor only.  I don't
know if it may affect more important faces as well.

Closing this bug, martin





      reply	other threads:[~2020-04-18  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-15 10:10 bug#40639: 26.3; Child frame border color not rendered when child frame has no minibuffer Alexander Miller
2020-04-15 17:20 ` martin rudalics
2020-04-15 17:32   ` Eli Zaretskii
2020-04-16  8:31     ` martin rudalics
2020-04-18  8:51       ` martin rudalics [this message]

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=c807be9f-8e02-f273-4c89-44b41f36cede@gmx.at \
    --to=rudalics@gmx.at \
    --cc=40639@debbugs.gnu.org \
    --cc=alexanderm@web.de \
    /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).