fix(frontend): respect PWA safe areas - #198
Merged
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
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.
Installed Safari PWAs can place the editor’s Back and Export controls beneath the status bar. Apply browser-provided safe-area insets to the app shell and size full-height screens to the remaining viewport.
Shared dialogs and drawers now respect the same insets, including landscape edges and the home indicator. Preserve the existing edge-to-edge viewport settings and consolidate drawer padding to avoid applying it twice.
Closes #197.
Validation:
pnpm preflightpassed (formatting, lint, type checks, knip, and repository tests).Real installed iPhone PWA validation, including the reported iOS 27 behavior, remains outstanding. No public API changes.