Skip to content

Wide screen only shows single column layout, very wasteful of horizontal space #5766

@winsphinx

Description

@winsphinx

Pre-submission Checklist

  • I have searched existing issues and confirmed this feature has not been requested
  • This is a feature request, not a bug report or question

Feature Area

User Interface (UI)

Problem or Use Case

Describe the bug / feature request

After the removal of Masonry layout in #5746, the memo list now only uses a single column layout even on very wide monitors (2560px, 3440px, ultrawide, 4K, etc.).

This makes the interface look extremely sparse and wastes a lot of horizontal space. For users who write many short memos, the single column feels very inefficient compared to the previous masonry/grid view.

Expected behavior

  • On wide screens, the memo list should display multiple columns (ideally 3~5 columns, or configurable).
  • On smaller screens, it should gracefully fall back to 2 or 1 column.
  • Either bring back an improved Masonry layout, or implement a simple responsive multi-column layout using CSS Grid / Multi-column / display: masonry (once widely supported).

Current behavior

  • Always single column on desktop, regardless of screen width.
  • Very poor space utilization on modern wide/ ultrawide monitors.

Thanks!

Proposed Solution

  1. Simple & fast: Use CSS column-count + break-inside: avoid with responsive breakpoints (3~4 columns on wide screens).
  2. Better long-term: Add a setting "Memo list columns" or "Layout mode" (Single / Multi-column / Masonry) with configurable min column width.
  3. Or use modern display: grid with grid-template-columns: repeat(auto-fill, minmax(280px, 1fr)) for a clean responsive grid.

Alternatives Considered

No response

Additional Context

No response

Contribution

  • I'm willing to submit a pull request for this feature

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions