@jwz@mastodon.social I’m on an OG M1 MacBook Pro that I use without external monitors cause… well this thing only ever really supported one and using software supported extra monitors sucks ass. The difference here is that I’m still on 27.0… man if they’ve fixed this in 27.0.1 I’m gonna be so dirty 😂 So on my system at least MacOS is handing out 0x0 child views into the screensaver window sometime *after* instantiating the animation. And then terminating the drawing surface before checking if the screensaver is cool with that. I assume native screensavers are doing what the patch does, which is wait for a window and then use the parent window dims to determine the drawing space. I could imagine the instantiate-window-late and whoops-sorry-didn’t-see-the-callback-there problems are race conditions (maybe), but the 0x0 child view bit seems deliberate… so if that’s an actual bug they fixed that’s gonna be *wild*.