bug#28872: 26.0.90; non-native-fullscreen does not play well with ns-transparent-titlebar on macOS

[Aaron Jensen]

On October 28, 2017 at 6:19:31 AM, Alan Third
(alan@idiocy.org(mailto:alan@idiocy.org)) wrote:

> On Wed, Oct 25, 2017 at 11:15:20AM -0400, Aaron Jensen wrote:
> > On October 25, 2017 at 6:38:23 AM, Alan Third
> > (alan@idiocy.org(mailto:alan@idiocy.org)) wrote:
> >
> > > In order to use lisp to do the fullscreen thing we’d need to keep
> > > track of various ‘windowed’ frame parameters, ie. undecorated, width,
> > > height, origin, maybe others. I assume it would be OK to stick them
> > > into the frame-parameters alist under a special key, so we know where
> > > they are when we want to switch back.
> >
> > This seems reasonable to me. I wonder if it would fix the lag when
> > full-screening that’s there now. That’s always bugged me.
>
> I’ve attached a half‐assed attempt at a lisp‐powered fullscreen for
> macOS. It won’t work elsewhere.
>
> At the moment it makes the frame too wide by 35 pixels. I seem to
> recall reading about that at some point, but I can’t remember if
> there’s a way to do it properly. It also seems to make the frame a
> little too tall.

There are some math problems when sizing or inspecting the size of
frames on macOS afaict. I have this package that I use to restore my
frame position on restart because desktop-save-mode doesn’t work well
for me (I think because of this bug) and I have to tweak the
dimensions by 20px x 4px when restoring:

https://github.com/aaronjensen/restore-frame-position/blob/862a72c65769fa9eee6f56434a1d649a6696ce23/restore-frame-position.el#L44-L49

> Maximising instead of resizing would work, but once the decorations
> are disabled maximise stops working, and maximising then removing
> decorations leaves a gap at the top of the screen.

Have you looked into how iTerm2 handles non-native full screen? There
are some notes in there about various things one must do to handle it:

https://github.com/gnachman/iTerm2/blob/d40c14de61c1574a58780967afd3c17583b33cd8/sources/PseudoTerminalRestorer.m#L138

The exact logic seems to differ based on whether or not it’s native
fullscreen and exactly which version of macOS it is. <= 10.10 and >=
10.11 behave differently, I guess.

Aaron