[codex] Improve Remote UI agent messaging and iPad header#4
Merged
Conversation
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
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
Root Cause
The iPad obstruction was not the normal status-bar safe area. It was the floating standalone/window control drawn over the left edge of the app, which is not represented by
safe-area-inset-top. The header now detects iPad-like standalone mode and reserves left-side space for that control. The subtitle shift came from only inserting the refresh icon while polling; the subtitle now keeps a persistent icon slot.Validation
bundle exec ruby test/remote_server_test.rbbin/testgit diff --checkipad-standaloneapplied,--ipad-header-control-space: 112px, header padding124px, and logo left edge atx=133on a 773px-wide viewport