6 ms·
I can accept the notch if the OS is smart enough not to render stuff behind it. Don't look at the notch as missing screen estate, look at the strips of display
by jeroenhd 5y ago
I can accept the notch if the OS is smart enough not to render stuff behind it. Don't look at the notch as missing screen estate, look at the strips of display next to it as extra screen you'd normally never have.
For now, the OS doesn't seem to be prepared not to render stuff behind the notch. That's a really obvious flaw that'll hopefully get patched out soon if Apple is worth their salt.
- happytoexplain 5y ago>the OS doesn't seem to be prepared not to render stuff behind the notch Really? UIKit has been successfully dealing with the notch for a long time, I assumed they would have updated AppKit with the same logic ("safe areas") way ahead of introducing notches to macOS. Have you seen examples where it's not working?
- least 5y agoQuinn from Snazzy Labs posted a video detailing the buggy nature of the notch on twitter [1]. [1] https://twitter.com/SnazzyQ/status/1453143510111059968 https://twitter.com/SnazzyQ/status/1453143510111059968
- happytoexplain 5y agoHoly shit! I wonder if this is something to do with some app devs not using the APIs as intended and it not mattering until now, but that seems so unlikely - surely the population of the menu bar is nigh-inescapably standardized (edit: double-unlikely, considering the battery icon example in that thread). It's always so disheartening to see screwups this obvious in the Apple ecosystem. The upside of their dictatorial style is supposed to be the absence of things like this.
- eclipxe 5y agoThe OS is smart enough to not render stuff behind it. You can test this by clicking a dragging a menu bar icon across the notch - it will immediately jump to the other side and not try to render a drag animation.