#1268 Search fields on the both sided are covered by Title bar in a full-screen mode

[scrutinizer]

Hello,
When in full screen I noticed that with the sidebars pulled the title bar does not go away completely like it does in Preview. Instead, it appears unhidden and half-covers the appropriate search fields (marked with red circles).

Steps to reproduce:

1. Toggle full-screen mode
2. Toggle the sidebars.
3. Move the cursor off the menu bar. The title bar remains in place covering the search fields.

Please, consider the screenshot for reference

[Christiaan Hofman]

What OS version do you have? I don't see this problem in 10.13.6.

I do not think we can fix this. The system code is responsible for moving
the toolbar in full screen and gives us no control over it.

[Christiaan Hofman]

I am a bit confused about the screenshot. This does not show a full screen window. In what state did you take the screen shot? When really in full screen, does the title bar automatically hide?

[scrutinizer]

Oops. I replied in a message but that seems not implemented with this forum.

My system is Lion.
Here how it looks in standard view

[scrutinizer]

A full screen mode of the same view:

[Christiaan Hofman]

This must be a bug in Lion. The window does not really go into full screen
mode. But that is precisely what the system code does. I do not see how we
could fix this. I think only you can fix this by upgrading your buggy
system.

[scrutinizer]

I think only you can fix this by upgrading your buggy
system

"or uninstall Skim" :)

[Christiaan Hofman]

Perhaps as a workaround you can set the SKAutoHideToolbarInFullScreen hidden preference for now. See the Wiki for details.

[scrutinizer]

I think I discovered something that I cannot find a credible explanation of with this hidden setting. I accidentally ran the full screen command without SKAutoHideToolbarInFullScreen key as

defaults write net.sourceforge.skim-app.skim -boolean yes

And I got the expected behaviour. When I noticed my mistake I immediately executed the command with the key added: it enabled auto-hide but left the fields half-covered by the top of the screen. I then omitted the key again and it ended up with what I initially wanted.
Here's why I have now.
And, btw, in Preview there's no such problem.

[scrutinizer]

That's when the cursor does not touch the top of the screen

Update. Upon re-launch the issue returned.

[Christiaan Hofman]

I'm copnfused now. When you run 'defaults write -app Skim SKAutoHideToolbarInFullScreen -bool true', what do you get? Does it automatically hide the toolbar, until you move the mouse over it? So does what you want?

[Christiaan Hofman]

BTW, you must run this command when Skim is not running.

[scrutinizer]

I ran these commands with Skim quit. Moreover, since that's not the issue with Preview I can only assume that the values for these sidebars are not calculated properly (if they are at runtime and weren't hard-coded by the developers) or, in either way, fail to establish correct settings in a full screen mode because even with the title bar hidden the sidebars extend over the visible area along the height of the screen instead of incrementing proportionally to adjust to the screens with 1400 x 900 size that my Mac falls under. I'm not an expert but I doubt that has to do something with bugs of PDFKit. To summarize I now can conclude to a high degree of certainity that the culprit is likely not the title bar but the way the app draws the sidebars in regard to the height of a screen. Maybe it's not the case with some other screen sizes (Retina or MBA) but apparently this could pretend to be a potential wrongdoer in my case.

[scrutinizer]

Check out a video-capture of the UI elements movement in Preview I made
http://vimeo.com/282065301

[Christiaan Hofman]

This has nothing to do with the sidebars and how they are calculated. They
are not calculated. They are just part of the content of the window. You
only see it with the sidebars because they have something distinguishable
at the top unlike the PDF, because that scrolls. It is the toolbar that
covers the window content. And that is a problem of that toolbar. We have
no influence over that, we only influence the content of the window, not
the window chrome at the top. So it is a big in the system. Other system
versions also do not do this. And that Preview may not have this problem
may not be relevant, they apparently auto hide the toolbar in full screen.
But that is and should not be a requirement, it is not even the default.

[Christiaan Hofman]

Let me add again: Apple's system code determines the broad layout of the window and the window chrome (titlebar, toolbar). Also in fullscreen. Apple only gives control of anything inside the content. (And btw, this is what we caclulate about the side bars in full screen: . That's right, nothing.) We have absolutely zero control over the layout of the window chrome and the size and location of the content view (certainly on 10.7). What you see is that the window chrome (toolbar) covers the top of the content. That is precisely what we have no control over. The system should place the (whole) content completely below the chrome, and it doesn't properly do that. That's a system bug (not PDFKit, as it ihas nothing to do with the PDF, but AppKit). Preview auto-hides the toolbar. We don't. This is an option (actually not autohiding is the system default!). This is and should never be a requirement. Perhaps it has to do with the fact that we don't use the default animation, which we need to do because of other requirements (and Apple forces us to). I don't know, and I don't control it. So it is Apple's bug, and Apple gives us zero control over this aspect. Apple has apparently fixed this bug in later OS versions. There is zero chance they will retroactively do so in 10.7.

[scrutinizer]

Umm okay, I understand. (BTW I know they "won't retroactively support my system" as much as I know that upgrades are not supported for every Mac computer). Well, that means that, whatever it might be, and despite the stated system requirements, I'm left with other option than to resolve this software conflict in favor of my system since the full-screen benefits are much required in my working envorinment.
My only suggestion for you would be to elevate mininal system requirements to the minimal version of OS X where the issue doens't exhibit.

Thank you for your replies.

[Christiaan Hofman]

As another workaround, you can also set a hidden preference to use the
legacy full screen feature.