Skip to content

🤖 fix: cap settings content width for readability#2420

Merged
ammario merged 1 commit intomainfrom
fix/settings-content-max-width
Feb 17, 2026
Merged

🤖 fix: cap settings content width for readability#2420
ammario merged 1 commit intomainfrom
fix/settings-content-max-width

Conversation

@ammar-agent
Copy link
Collaborator

Summary

Bound the settings content pane width so forms and text stay readable on very wide windows.

Background

Without a max width, settings fields stretch across the full available area, which makes scanning labels and controls harder.

Implementation

Wrapped the rendered section component in SettingsPage with a w-full max-w-5xl container while preserving the existing scroll/padding layout.

Validation

  • make static-check

Risks

Low. This is a layout-only change scoped to the settings content container.


Generated with mux • Model: openai:gpt-5.3-codex • Thinking: xhigh • Cost: $0.00

@ammar-agent ammar-agent force-pushed the fix/settings-content-max-width branch from a609701 to afe11e4 Compare February 13, 2026 16:44
Wrap the settings section content in a max-width container so long forms remain easier to scan on wide windows.

---

_Generated with `mux` • Model: `openai:gpt-5.3-codex` • Thinking: `xhigh` • Cost: `bash.00`_

<!-- mux-attribution: model=openai:gpt-5.3-codex thinking=xhigh costs=0.00 -->
@ammar-agent ammar-agent force-pushed the fix/settings-content-max-width branch from afe11e4 to 49b2725 Compare February 17, 2026 01:21
@ammario ammario merged commit 491e03c into main Feb 17, 2026
18 checks passed
@ammario ammario deleted the fix/settings-content-max-width branch February 17, 2026 01:22
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