Skip to content

fix: respect mobile auth insets and unify goal sheets - #39

Merged
Eoic merged 1 commit into
developmentfrom
fix/mobile-auth-and-goal-sheets
Oct 6, 2026
Merged

Eoic merged 1 commit into
developmentfrom
fix/mobile-auth-and-goal-sheets

Conversation

@Eoic

@Eoic Eoic commented Oct 6, 2026

Copy link
Copy Markdown
Member

Summary

Mobile authentication footers could sit behind Android navigation controls. Add a bottom safe area to the shared mobile auth layout, covering login, registration, and password recovery while retaining keyboard resizing.

Use the standard title/close header for active and completed Goal details sheets. Give completed goals a Done action with Delete as the secondary action, and allow labels to wrap on narrow phones. Include the pending lockfile quoting normalization; the reader revision is unchanged.

Testing

  • ../tools/papyrus test client -- test/widgets/auth/auth_page_layouts_test.dart test/widgets/goals/goal_details_sheets_test.dart: all 11 tests passed.
  • ../tools/papyrus check client: formatting, analysis, and four web-bootstrap checks passed.
  • git diff --check origin/development...HEAD: passed.

The regressions simulate Android navigation insets and an open keyboard, and check Goal sheet actions at 320 and 390 pixels, equal button sizing, overflow, and dismissal. The full application suite was not rerun locally.

UI evidence

Inspected locally rendered login, active Goal, and completed Goal screenshots at 390 × 844. No new Android device build was installed for this change.

Compatibility and migration

No data migration or version bump. Goal persistence and authentication behavior are unchanged. Merging into development does not publish a release.

Notes

This PR contains the existing mobile layout fixes. The broader Goals management redesign will be handled separately.

Checklist

  • The branch, commits, and pull request title follow the repository conventions.
  • The change is complete and limited to the agreed scope.
  • Relevant tests have been added or updated.
  • Formatting, analysis, and tests pass.
  • Documentation, UI evidence, and migration notes are included where relevant.
  • No credentials, personal data, copyrighted fixtures, or unrelated generated files are included.
  • The branch is up to date with its target branch.

Copilot AI balanced review requested due to automatic review settings October 6, 2026 11:42

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review ✅ Completed 2026-10-06T11:45:21.558397Z 5d61e02 PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5d61e023f0

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment on lines +35 to +36
body: SafeArea(
top: false,

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Limit the safe area to the bottom inset

On devices with nonzero horizontal safe-area padding that still select MobileAuthLayout—for example, a notched phone in landscape at 600–839 logical pixels—the default left and right settings also inset the entire column. This narrows CompactAuthHeader and leaves surface-colored gutters beside the formerly full-width clipped hero, even though this change only needs bottom protection; disable the horizontal insets or apply the bottom safe area below the hero.

AGENTS.md reference: AGENTS.md:L22-L24

Useful? React with 👍 / 👎.

@Eoic Eoic self-assigned this Oct 6, 2026
@Eoic
Eoic merged commit 3ffd396 into development Oct 6, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants