Subject: bug#25511: 26.0.50; modify-frame-parameters modifies undesignated parameter?

From: Noam Postavsky <[email-masked]>
Date: Mon, 23 Jan 2017 12:27:23 -0500

On Mon, Jan 23, 2017 at 3:03 AM, martin rudalics <[email-masked]> wrote:
>
>> On the new frame, (frame-parameter nil 'left) returns 8, that is
>> outside of the down screen.  This happens whichever the original
>> frame (that runs the script) exists in the up screen or the down
>> screen.  As mentioned above, a new frame did not protrude from
>> the down screen last week.  Here is a workaround:
>>
>> (let ((frame (make-frame)))
>>    (sit-for 0)
>>    (modify-frame-parameters frame '((top . 1200))))
>>
>> But it is needless, isn't it?
>
> IIUC your approach worked because of a busy loop in x_make_frame_visible
> which has been removed a few days ago.  I back its removal so you should
> be able to do without it.

Should we change modify-frame-parameters to delay the actual
modification until the frame turns visible?