Skip to content

fix(settings): align the Appearance tab with the other settings pages - #653

Merged
A-EDev merged 1 commit into
mainfrom
fix/appearance-tab-padding
Nov 16, 2026
Merged

A-EDev merged 1 commit into
mainfrom
fix/appearance-tab-padding

Conversation

@A-EDev

@A-EDev A-EDev commented Nov 16, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Settings > Appearance no longer centers itself in a narrower column, so it starts at the same left edge and uses the same width as the other settings pages.
  • Changelog line under SETTINGS.

Related issue

Change type

  • Bug fix
  • Feature
  • Refactor or maintenance
  • Documentation
  • Build, packaging, or CI

Validation

Run on a branch that merges this PR with the other two UI PRs from the same batch (frontend only, no Rust changes):

  • pnpm test: 456 files, 2706 tests, 0 failures
  • pnpm build: tsc and vite build pass
  • cargo fmt --manifest-path src-tauri/Cargo.toml --all -- --check
  • cargo clippy --manifest-path src-tauri/Cargo.toml --all-targets --all-features
  • cargo test --manifest-path src-tauri/Cargo.toml --all-targets --all-features
  • I smoke-tested the affected desktop behavior.

OS: macOS dev build only. In the dev app the Appearance title now sits at the same x position as the Profiles title.

Screenshots or recordings

Risk and compatibility

Frontend layout only. No migrations, database, network, permission or background work changes.

  • No new secrets, private data, telemetry, or broad Tauri permissions were introduced.
  • User-facing documentation was updated where needed.
  • Dependency and lockfile changes are intentional and limited to this PR.
  • Breaking changes and upgrade steps are clearly documented.

@A-EDev
A-EDev merged commit e796b75 into main Nov 16, 2026
11 checks passed
@A-EDev
A-EDev deleted the fix/appearance-tab-padding branch November 16, 2026 18:31
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