refactor(step2): hide the map below xl instead of stacking it#254
Merged
Conversation
The map is an optional spatial-context aid, not load-bearing for the sample workflow. When the viewport doesn't have room for a real 3-col layout it's better to drop the map entirely than to either squeeze it under the form (extra scroll, dead space) or shrink the side cols. New behavior on both Inquiry- and RecoveryStep2: - < lg : single column stack — addresses, then form. - lg-xl : addresses + form (2 cols), map hidden. - xl+ : addresses + form + sticky map (3 cols, unchanged from today). Drops the order-2 / order-3 flex-ordering tricks — no longer needed since the form always follows the addresses card on every breakpoint — and removes the h-64 mobile thumbnail height now that the map never shows on small screens. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
Per feedback after #253: the map is an optional spatial-context aid, not load-bearing for the sample workflow. When the viewport doesn't have room for a real 3-col layout it's better to drop the map entirely than to either squeeze it under the form (extra scroll, dead space) or shrink the side cols.
Touches both InquiryStep2 and RecoveryStep2 — same shape, same fix.
New behavior
Drops
Test plan
🤖 Generated with Claude Code