Skip to content

[Design V2] Text step editor collapses to a few pixels at mobile widths #1145

Open

Description

@saurav-shakya

Bug Report 🐛

Part of #1096

At phone widths the text.md editor on the Text step is about 5px tall, so you cannot read or edit the template. The help rail ("This step needs" / "Why this step") fills the screen instead.

Expected Behavior

The Text step editor has enough height to read and edit the template, like the Logic step does since #1104.

Current Behavior

The editor is about 5px tall at 390×844. Measured height of the Monaco editor on the Text step:

Viewport Editor height
390×844 (phone) 5px
768×1024 (tablet) 313px
1366×850 (desktop) 459px

Possible Solution

Under 960px .nd-view-editor stacks the editor column above the help rail. #1104 gave the Logic step a fixed editor height and a scrolling body in that layout. The Text step did not get the same change, so its flex column shrinks to almost nothing. Applying the same rules to .nd-view-text fixes it.

Steps to Reproduce

  1. Open the playground at a phone width (Chrome DevTools, iPhone 12 Pro, 390×844).
  2. Click Got it on the banner, then Start building →.
  3. On Consulting Agreement, click Start with this template →.
  4. You land on Step 2 · Text, and the editor shows no lines.

Context (Environment)

Trying to edit a template on a phone in Design V2.

Desktop

  • OS: Linux
  • Browser: Chromium
  • Version: current main (d7a0a9b)

Detailed Description

Only the Text step is affected this badly. The Data step is also cramped at this width, but that is a separate issue.

Possible Implementation

CSS only, inside the existing @media (max-width: 960px) block, mirroring #1104 for .nd-view-text, plus an e2e test at 390×844.

I'd like to work on this.

Activity

  1. saurav-shakya commented on Nov 22, 2026

    @saurav-shakya
    Author

    I'm working on this; the fix is ready and I'll open a PR shortly.

  2. mira-accord-project commented on Nov 22, 2026

    @mira-accord-project

    Thank you for the detailed report, including the measurements and steps to reproduce. That makes the problem easy to confirm. We can see that pull request #1146 is open and linked to this issue. The maintainers will review it there and follow up on the PR with any changes needed. As the issue suggests, keeping the fix to CSS inside the existing mobile breakpoint, with an e2e test at 390x844, would help that review. Thanks for taking this on.


    Posted automatically by Mira, an Accord Project agent. A maintainer will follow up; they make the decisions on this.

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