Skip to content

CM6: Line numbering misalignment, temporary font-size compression and unexpected fold arrow rendering on larger screens #4144

Closed

Description

@yugalkaushik

p5.js version

No response

What is your operating system?

None

Web browser and version

No response

Actual Behavior

In the cm6 branch, the editor UI has a few visual inconsistencies compared to the current editor implementation.
The current editor (attached preview) renders correctly with proper line number alignment, stable spacing and expected behavior. However, in the cm6 branch, there are multiple UI regressions affecting readability and layout consistency.

  1. Line number alignment is off
  2. Font-size change causes temporary compression
  3. Unexpected function closing/fold arrow rendering on larger screens

Expected Behavior

The cm6 editor should match the behavior and visual consistency of the current editor:

  1. Properly aligned line numbers
  2. Stable layout during font-size changes (no temporary compression)
  3. No unexpected fold/function arrow rendering on larger screens

Steps to reproduce

Steps:

  1. Open the editor
  2. Open settings and try changing the font size

CM6 preview:
https://github.com/user-attachments/assets/fae89573-5b8a-4dbb-bc1f-f5ec79fc939d

Image

Expected/Current:

preview-editor.mp4

Activity

  1. parthjadhao01 commented on Jun 2, 2026

    @parthjadhao01
    Contributor

    Hi @khanniie, I'd like to work on this once it gets approved.

  2. khanniie commented on Jun 2, 2026

    @khanniie
    Member

    Hi @khanniie, I'd like to work on this once it gets approved.

    @parthjadhao01 sounds good! Thank you!

  3. yugalkaushik commented on Jun 2, 2026

    @yugalkaushik
    ContributorAuthor

    @parthjadhao01 Just a suggestion, before directly jumping into the fix, check the develop branch first and compare the methods and CSS being used there with what is currently missing in the codemirror branch. It will help you understand the existing implementation better and identify gaps before making changes in the codebase.

  4. parthjadhao01 commented on Jun 2, 2026

    @parthjadhao01
    Contributor

    Thanks for the suggestion! I'll make sure to check the develop branch first before making any changes

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

Metadata

Metadata

Assignees

Labels

BugError or unexpected behaviors

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions