Add per-display-mode safe area insets from live host sync#30
Merged
Conversation
Extracted real safe area values from production ChatGPT and Claude. ChatGPT reports bottom: 150 in fullscreen; Claude reports insets on all four sides (top: 16, right: 16, bottom: 138, left: 16). The inspector now auto-applies safe area when switching display modes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
safeAreaByDisplayModeto theHostShellinterface so each host can declare safe area insets per display modebottom: 150, Claude fullscreentop: 16, right: 16, bottom: 138, left: 16safeAreaandstylesper display mode so this data is collected automatically on future syncsTest plan
pnpm --filter sunpeak validate