Skip to content

[Bug]: Android Queued messages sheet misses Material rounded corners #14931

Closed

Description

@PixPMusic

Before submitting

  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.

Area

apps/mobile

Steps to reproduce

  1. Open a thread in the Android app using the Material layout.
  2. Queue a follow-up message while work is active.
  3. Open the queued-message pill.
  4. Compare the content below the Queued header with other Material content panes.

Expected behavior

The Android sheet's outer top edge and content pane use the established Material rounded top corners and split-view inset.

Actual behavior

The sheet's outer top edge and the list pane have square top corners.

Impact

Cosmetic issue

Version or commit

main @ 7ff2eab

Environment

Android Material layout; reported on a foldable in split view.

Screenshots, recordings, or supporting files

Sanitized native before/after evidence will be included in the focused fix PR.

Activity

  1. juliusmarminge commented on Oct 2, 2026

    @juliusmarminge
    Member

    Note

    Grok responding on behalf of Julius.

    Triage

    Thanks for the report, @PixPMusic! I confirmed this on main at 7ff2eabf56, where the queued-sheet file is unchanged. It's a real Android-only visual gap, and I didn't find a duplicate.

    ThreadQueue is a form sheet. On Android, ThreadQueueSheet draws the header and the list directly on bg-sheet: AndroidSheetHeader keeps its bottom border, and the list isn't wrapped in MaterialScreenContent. That wrapper is what gives the other Material surfaces a bg-header band behind rounded-t-[28px] content. Git overview uses it, and in split layouts (usesSplitView, windows at least 720 wide and 600 tall) it also passes insetHorizontal, which adds the 4px side inset. The thread canvas uses the same 28px top radius. So the join between the Queued header and the list is square at every Android size, and the split-layout inset is missing on wide windows, including an unfolded foldable.

    iOS isn't affected. MaterialScreenContent returns its children unchanged on other platforms, and the iOS sheet uses the nested native header.

    The Agents sheet has the same gap and is already tracked in #14920 (open PR #14925 only touches that sheet), so this issue can stay scoped to Queued. The fix would be to wrap the Android list in MaterialScreenContent, hide the header's bottom border, and pass the split-layout inset the same way Git overview does. Behavior and navigation wouldn't change.

  2. added
    bugSomething is broken or behaving incorrectly.
    via-triageFiled through npx t3 triage
    on Oct 2, 2026
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

    bugSomething is broken or behaving incorrectly.via-triageFiled through npx t3 triage

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions