bug#14841: Frames created invisible have their visibility parameter set to t

[Juanma Barranquero <lekktu@gmail.com>]

On Thu, Jul 11, 2013 at 6:29 PM, Eli Zaretskii <eliz@gnu.org> wrote:

> But it doesn't say anything about frames created invisible.  It talks
> about frames that are visible, but obscured.

Yes. The code that decides that a frame is "visible, but obscured"
could be interpreting a just created invisible frame as obscured.
That's what I though. Seems I was wrong.

> Can you provide a recipe to reproduce this, starting with "emacs -Q"?

My IELM example was from emacs -Q, but OK:

  emacs -Q
  M-: (make-frame '((visibility))) <RET>
  M-: (mapcar #'frame-visible-p (frame-list)) <RET>
  => (t t)
  M-: (make-frame-invisible (make-frame)) <RET>
  M-: (mapcar #'frame-visible-p (frame-list)) <RET>
  => (nil t t)
  M-: (setq f (make-frame)) <RET>

At this point, C-x 5 o does not take you to the previous frame.
Presumably, because Emacs gets confused that some previous frame,
which is invisible, is "visible" because its visibility parameter says
so. Then

  Select the initial frame.
  M-: (make-frame-invisible f) <RET>
  M-: (mapcar #'frame-visible-p (frame-list)) <RET>
  => (nil nil t t)