Skip to content

Prevent network address values from overlapping labels - #8741

Open
avk458 wants to merge 1 commit into
basecamp:quattrofrom
avk458:fix-network-address-layout
Open

Prevent network address values from overlapping labels#8741
avk458 wants to merge 1 commit into
basecamp:quattrofrom
avk458:fix-network-address-layout

Conversation

@avk458

@avk458 avk458 commented Aug 28, 2026

Copy link
Copy Markdown

What

Give the IP address and gateway values the remaining three columns in the network details grid. Each value now uses its own row.

Why

IPv4 addresses can exceed the width of one value cell and draw over the adjacent labels. This occurs in the stock panel at the default 12 px text size.

This uses the same full-width layout that #8683 applies to long IPv6 values, but fixes the existing IPv4 fields independently.

Testing

  • bash test/shell.d/network-test.sh
  • Verified in the running Omarchy 4.0.1 shell at the default 12 px text size
  • Confirmed that the IP address and gateway are fully visible with no overlap

Copilot AI balanced review requested due to automatic review settings August 28, 2026 10:00

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Prevents IPv4 values from overlapping adjacent labels in the network details grid.

Changes:

  • Gives IP address and gateway values three-column spans.
  • Places each value on its own row.

Tip

If you aren't ready for review, convert to a draft PR.
Click "Convert to draft" or run gh pr ready --undo.
Click "Ready for review" or run gh pr ready to reengage.


💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@avk458

avk458 commented Aug 28, 2026

Copy link
Copy Markdown
Author

Before

Network panel before: IP address overlaps adjacent labels

After

Network panel after: address values use full rows

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