Skip to content

Mobile drawer breaks at tablet/iPad widths (≥768px) #91

Closed

Description

@yigitdot

Context

The mobile drawer introduced in PR #56 (and polished across PR #89) is gated to phone-only via @media (min-width: 768px) { .mm-toggle, .mm-overlay, .mm-panel { display: none } } in app/globals.css. At ≥768px the drawer disappears and the desktop nav takes over: full Docs/Blog/Litepaper cluster + section anchors (compare / method / faq / contact).

That breakpoint was correct for a phone-vs-desktop split but reads broken at tablet widths — the iPad portrait viewport (~768–834px) and similar tablet sizes get the desktop nav, which crowds at those widths even though the device has plenty of touch surface to host a drawer.

Symptom

On iPad portrait and similar tablet widths, opening the page shows the desktop nav. The right cluster (Docs / Blog / Litepaper, each with an arrow) plus the centred section anchor list compete for the available width, the touch targets are tight, and the editorial breathing room collapses.

Proposed direction (not committed)

A few options worth weighing in design before code:

  1. Lift the drawer breakpoint to ≥1024px (or thereabouts). Easy, but inherits the drawer's min(88vw, 380px) panel width — on a 1024px iPad that's still ~380px, which looks small against the rest of the viewport. The panel proportion likely needs to scale.
  2. Drawer panel width scales by viewport — keep 88vw on phones, lift to ~48vw on tablets, cap at ~520px. Same drawer language, tablet-appropriate scale.
  3. A second, distinct tablet nav variant — neither the phone drawer nor the desktop cluster, but a hybrid (e.g. desktop cluster collapsed into a single "menu" pill that opens an inline dropdown). Most work, most refined.

Lean toward (1)+(2) unless design wants to invest in a separate tablet treatment.

Related

Out of scope here

  • Touching the desktop (≥1280px or wherever the eventual upper bound lands) nav. That's working as intended.
  • Reworking the drawer's open/close choreography. The phone version is good; tablet should inherit, not reinvent.

Activity

  1. self-assigned this
    on May 11, 2026
  2. added a commit that references this issue on May 11, 2026
    4ca9a8a
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

Priority

None yet

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions