Skip to content

fix(auth): phone-login form layout breaks on live mobile (#944 follow-up) - #1006

Merged
developer-ainative merged 1 commit into
mainfrom
fix/944-phone-login-css-layout
Oct 7, 2026
Merged

developer-ainative merged 1 commit into
mainfrom
fix/944-phone-login-css-layout

Conversation

@developer-ainative

Copy link
Copy Markdown
Contributor

Live-verified in a real mobile-width browser session right after #1005 merged and deployed: the email-form escape hatch (and the phone form itself) rendered with giant overlapping sideways buttons instead of a stacked layout. Screenshot-confirmed, not just inferred from code.

Root cause: .m-auth-fields-email and .m-auth-phone-form both set display: flex with no flex-direction anywhere in the file, so flex defaulted to row for their children (form fields, submit button, OAuth button).

This was called out as a deferred minor in #1005's review ("no dedicated CSS for .m-auth-escape/.m-auth-error") — live testing showed the real impact is worse than cosmetic, it's a genuine layout break on the exact device this feature targets. Fixing immediately rather than leaving it deferred.

Also adds basic .m-auth-escape button styling (was fully unstyled browser-default).

No test changes — this is pure CSS; verified via tsc --noEmit, the existing Auth component test suite (10/10 pass, unaffected since jsdom doesn't load stylesheets), and will re-verify visually against production after merge.

…-up)

Live-verified in a real mobile browser after merge: .m-auth-fields-email
and .m-auth-phone-form had display:flex with no flex-direction, so their
children (form fields, submit button, OAuth button) laid out in a row
instead of stacked. On the actual target device (<=760px) this made the
email-form escape hatch render as giant overlapping sideways buttons --
confirmed by screenshot, not just inferred from code.

This was flagged as a deferred minor ("no dedicated CSS") in the prior
fix-pass review, but live testing showed it's a real layout break, not
just unstyled controls -- fixing now rather than leaving it deferred.
@developer-ainative
developer-ainative merged commit da1b4ba into main Oct 7, 2026
1 check 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.

1 participant