insidegui / WWDC

The unofficial WWDC app for macOS
https://wwdc.io
BSD 2-Clause "Simplified" License
8.6k stars 777 forks source link

Bottom of screen not visible on 1366 x 768 displays #623

Closed tarasis closed 4 years ago

tarasis commented 4 years ago

Before opening your issue, please make sure you answer YES to all of the questions below.

If you answered YES to all of the questions, please provide as much information as possible about your issue.

When running the app on a 1366 x 768 display, the bottom of the app is chopped off. You can only just see the tops of the Related Sessions. While it is possible to resize the app horizontally, you can not resize vertically, nor can you scroll the session view.

This the how the app looked zoomed to fill the screen. You can see at the bottom the related sessions are chopped. WWDC App Zoomed

If you then swap to full screen, you can now see all the related sessions, but the top of the video is chopped off. WWDC App Full Screen

Just running the app normally

Running app on 11" MacBook Air, its res is 1366 x 768

Open app on a 1366x768 screen. Select a session.

Additional quirk. Sometimes the related sessions aren't visible at all, but if you swipe up into mission control, and then swipe out of it again, the contents resize themselves and the related sessions appear. (However this doesn't work if you use App Expose)

Selected a session, presently the related sessions aren't visible. Related Sessions not visible

After using Mission Control (swipe 3 fingers up, then either swipe 3 fingers down, or just click on the window), the contents resize slightly and the related sessions are visible.

Related Sessions visible after using Mission Control

allenhumphreys commented 4 years ago

The good news here is we've moved to a scroll view for the session summary. This keeps the maximum window height to 733 pixels. This hopefully will just barely squeeze into your display. Any chance you could confirm via building master directly?

tarasis commented 4 years ago

I can build it, just might take a while on this thing. will report back later and thanks for the swift reply.

insidegui commented 4 years ago

I had the same issue, which prompted #617, so this has already been fixed 🥳