Gmail layout

Open
#781 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

@salmonumbrella is already working on this.

Since Nov 13, 2026.

  • #786 by @salmonumbrella — open

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
1/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
javascript
Domain
design, frontend

Research direction

The issue describes the Gmail layout and links a ready branch with a 39-file diff, but says the author is holding it pending a maintainer decision and other PRs. Read the linked comparison and inspect the layout entry points, tests, and translations it changes. The work is complete when the layout is available in both settings and the toolbar menu and the described frontend checks pass; wait for the maintainer's decision before starting.

Written by the indexing model from the issue text.

Description

The situation

A lot of people come to MailFlow from Gmail, and I use it as the front end for my Gmail accounts. Every layout today keeps MailFlow's own arrangement, so moving over still means relearning where things are. I'd like a Gmail layout: search across the top, Compose and folders on the left, a full-width list with a checkbox and star on every row, and a message that opens in place of the list.

It's one more option in Settings → Appearance → Layout and in the toolbar's layout menu, next to Focused, Compact and the rest. Selecting, starring, search, compose, the reader and GTD are all MailFlow's existing ones.

Long threads read the way they do in Gmail too:

  • With 5 or more messages, the collapsed ones in the middle fold into one "N older messages" row.
  • The newest message and every unread one open on arrival.
  • Expand all and Collapse all sit in the conversation bar, and Reply, Reply all and Forward sit under the last message.
  • Quoted history at the end of a reply hides behind a "•••" toggle, in conversations and in the single-message reader. Forwards are never trimmed.

What works today, and why it is not enough

List first comes closest (full-width list, a message opens on its own), but rows keep MailFlow's arrangement, search stays in the list toolbar, and the checkbox and star only show up in Select mode or on hover. Custom CSS can restyle things, but it can't move search into a header or add row controls.

https://github.com/user-attachments/assets/0cf46a2f-800e-4cc2-8c31-46cb71665ce8

The video is Chrome against a fixture with made-up mail, in the Dark theme with dark email bodies and GTD on: picking the layout, rows, a long conversation, a single email with a reply chain below it, Mark done and t to Todo, compose, a 900 px window and a phone. Email bodies follow the theme exactly as in the other layouts.

The PR is ready

https://github.com/salmonumbrella/mailflow/tree/feat/gmail-layout, 12 commits on current main (diff).

  • Opt-in. Nothing changes unless you pick Gmail, and all of its CSS sits under [data-mailflow-layout="gmail"].
  • Frontend only: no backend change, migration or new dependency.
  • Rows and the reader size themselves to the pane, not the window (a small ResizeObserver hook), so it holds up with both sidebars open, at 150% text and on a phone.
  • Quoted history is trimmed when the frame document is built, with <details>, so the frame's sandbox and CSP are unchanged. It recognizes Gmail, Apple Mail, Thunderbird, Outlook and Yahoo quotes, and plain-text > lines.
  • +2495/−133 across 49 files: about 710 lines of component changes, 500 of CSS, 1150 of tests, and the new strings in all 11 languages.
  • Frontend lint, tests and build pass, apart from 5 shortcut tests that also fail on main when run on macOS.

What I need from you

A yes or no on a Gmail layout in core. I already have PRs open, so I'll hold this one until you say yes and one of those is done.

Dominant language
JavaScript
Stars
518
Forks
50
Avg merge
4d 45m
Merged PRs (30d)
43

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from maathimself/mailflow

All issues in maathimself/mailflow

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.