learningequality / learningequality/studio

[RTE] Edit icon overflows container when text line is too long

Open
#5,934 0 comments 0 reactions 1 assignee View on GitHub

@AlexVelezLl is already working on this.

Since Aug 25, 2026.

bug DEV: frontend P1 - important
Dominant language
Python
Stars
191
Forks
307
Avg merge
5d 6h
Merged PRs (30d)
10

Description

This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Observed behavior

When the question field's Rich Text Editor (RTE) contains a long, unbroken line of text (no spaces or word-wrap opportunities), the edit (pencil) icon overflows outside the right boundary of the RTE container and renders floating to the right of it.

Image

Expected behavior

The edit icon should not escape the RTE container when content overflows. The correct behavior is TBD — either the icon floats on top of the content (with a background) or remains fully contained within the box — but in either case it should not render outside the container boundary.

User-facing consequences

Content creators building exercises in Studio see a broken layout when entering long, unbroken text in a question field — the edit icon renders outside the RTE container, making the assessment editor look visually incorrect.

Steps to reproduce

  1. Create a new exercise node in Studio.
  2. Add a question.
  3. In the question field, type a long string of text with no spaces or word breaks (e.g., TestestestTestestest... repeated many times).
  4. Observe that the edit (pencil) icon overflows outside the right boundary of the RTE container.

AI usage

Used Claude to help draft this issue from a description and screenshot. Reviewed and confirmed all sections for accuracy.

Contributor guide

Open the contributing guide

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.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.