Quantcast

fullscreen multiwindow OS X bug?

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

fullscreen multiwindow OS X bug?

René J.V. Bertin
Hi,

I ran into what looks to be a bug in Apple's fullscreen algorithms. On 10.9.5 with screens DO NOT have separate spaces:

1) open a Terminal.app window, write down the shell's PID
2) make it fullscreen using the titlebar button
3) open a new window using Command-N
4) exit from fullscreen mode

You could expect the window created in step 3) to remain a normal window but instead it is made fullscreen too. What's more, it somehow replaces the original fullscreen window which is MIA after step 4). MIA but not closed: it still shows up in the windows menu, and the shell (with PID recorded in step 1)) is still running.

Same happens with a Qt-based console emulator so this is not a bug in Terminal.app .

Is this a known bug (google hasn't been my friend yet finding that answer)?

If not, I'd love to know in what other Mac OS versions this bug can be reproduced and if it depends on the screensHaveSeparateSpaces setting. I'll probably have to upgrade to 10.11 or 10.12 sometime soonish but if anyone is willing to run the few simple steps above I'd really appreciate it.

Thanks,
René
db
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: fullscreen multiwindow OS X bug?

db
On 20 Apr 2017, at 19:21, René J.V. Bertin <[hidden email]> wrote:
> I ran into what looks to be a bug in Apple's fullscreen algorithms. On 10.9.5 with screens DO NOT have separate spaces:
> ...
> Same happens with a Qt-based console emulator so this is not a bug in Terminal.app .

I couldn't reproduce it on 10.8.5. Have you tried switching between the windows using the Window menu or ⌘1, ⌘2, etc?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: fullscreen multiwindow OS X bug?

René J.V. Bertin
On Thursday April 20 2017 23:20:33 db wrote:

> > Same happens with a Qt-based console emulator so this is not a bug in Terminal.app .
>
> I couldn't reproduce it on 10.8.5. Have you tried switching between the windows using the Window menu or ⌘1, ⌘2, etc?

Ah, thanks, so this appears to be a regression introduced with 10.9.x . Does 10.8 already have the 2 different Spaces (Mission Control) modes?

To answer your question: yes, I did try the Window menu as well as the "show all windows" option under the Dock tile. Something does appear to change when I select the "MIA" window, but it doesn't reappear. I can have faith though and use Command-W to close the window after selecting it that way.

FWIW, as can be expected Safari is affected too.

I just notice that after selecting the MIA window, the fullscreen menu item reads "Exit Full Screen". IOW, the window remained in fullscreen mode and I can retrieve the window via that menu item.

That suggests a partial explanation. Apple uses a temporary Space to provide the fullscreen environment, apparently one for each window made fullscreen. Opening a new window and making it fullscreen switches to that window's Space and when you then exit fullscreen mode there is no way to go back to the other fullscreen window's Space.
That's confirmed when you switch to a different app when in fullscreen mode; there's no way to go back to that fullscreen window. Even if I set "when switching to an application, switch to a Space with open windows for the application".

All this doesn't happen when you use a basic fullscreen implementation that removes window decoration (titlebar, frame etc) and resizes the window to cover the full screen. Much faster, too, and you get to keep access to all other screens. But, apparently that's "non-platform behaviour" ...

R.
Loading...