Bug: Notch Support

[kebot]

• Place Window in Notch Area
• Calculate Notch Size for web use

[kebot]

Check the code in: https://github.com/navtoj/NotchBar/tree/main

Claude Code:

⏺ Perfect! Now I understand how NotchBar positions its window under the notch. Here's how it works:

Window Positioning Strategy

NotchBar uses a clever multi-layered approach:

Full-Screen Transparent Window (AppWindow.swift:20)

The window is created with the same frame as the built-in screen:
contentRect: NSScreen.builtIn.frame
This makes it cover the entire screen, including the notch area.

Window Configuration (AppWindow.swift:32-44)

Key properties that enable positioning under the notch:

Level: Set to normalWindow + 1 so it sits above normal windows
Collection Behavior: canJoinAllSpaces, stationary, fullScreenNone, ignoresCycle - makes it persist across all spaces
Transparent: backgroundColor = .clear, isOpaque = false, hasShadow = false
Fixed: isMovable = false prevents user repositioning

Notch Detection (NSScreen.swift:53-76)

The notch property calculates the notch area using:

auxiliaryTopLeftArea and auxiliaryTopRightArea - these are macOS APIs that define the areas on either side of the notch
safeAreaInsets.top - gives the notch height
The notch frame is calculated as the gap between these two auxiliary areas

Content Layout (AppView.swift:17-70)

The UI is positioned using:

An HStack with spacing equal to notch.width (line 19)
Left widgets constrained to maxWidth: notch.minX (line 30)
Right widgets also constrained to maxWidth: notch.minX (line 63)
The entire bar set to maxHeight: notch.height (line 66)

The window stays locked in position through observers that reset the frame if it ever moves or resizes (AppWindow.swift:48-49).

The key insight is that NotchBar doesn't specifically position under the notch - it creates a full-screen transparent window and only draws content in the areas flanking the notch, making it
appear as if it's "under" the notch.