Skip to content

[Feature]: Make Working, Snoozed, and Settled sidebar sections easier to distinguish #38709

Closed as not planned

Description

@daniyal-rahman

When Working, Snoozed, and Settled are expanded in the sidebar, their headers blend into the thread rows. It is hard to see where one section ends and the next begins, especially in a long list. This is about sidebar sections, not the selected conversation tab.

Give each section a clearer boundary using T3's existing theme colors: a subtle neutral header band, a visible divider even beside the count. Keep the labels, counts, expand/collapse controls, and thread status indicators intact.

Check with all three sections expanded, collapsed, and mixed; long lists; light/dark themes; hover and keyboard focus. The boundary should remain readable without depending on color alone.

The original version of this issue misread “working tab” as the selected conversation tab. This body corrects that scope.

Related implementation: #26403 already restores the hidden divider. The additional treatment proposed here gives the headers a neutral band and stronger label contrast, scoped to the sidebar shelves. Keeping the original 32px header height matters because sidebar drag projection relies on it.

A small implementation is available on my fork: daniyal-rahman@5a7d493c

Verification: vp run check:changed --concurrency 1 passed (format, lint, both knip passes, affected typechecks, React compiler checks). Light/dark mocks used the real redesign components with synthetic thread content; the isolated main app also rendered the new variant on the Settled header. The full three-section fixture was only checked in the redesign preview. No installed app was changed.

Activity

  1. changed the title [-][Feature]: Make the selected conversation tab easier to distinguish[/-] [+][Feature]: Make Working, Snoozed, and Settled sidebar sections easier to distinguish[/+] on Nov 18, 2026
  2. juliusmarminge commented on Nov 18, 2026

    @juliusmarminge
    Member

    Thanks for writing this up. It asks for new behaviour rather than reporting a defect, so it does not belong in the bug tracker and I'm closing it as not planned here. Feature ideas are discussed in Discussions: please post it there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions