learningequality / learningequality/studio

(unstable) mobile keypad seems to not work for formula editor

Open
#6,112 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
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

On unstable (this is not live on prod) there is the "mobile keypad" for the fomula editor. However, at least on chrome dev tools, it seems like the focus "outside" of the RTE is returning the editor to a "closed" state and not allowing inputs from the touch screen keyboard.

This should be reproduced on a physical device.

Errors and logs

https://github.com/user-attachments/assets/0ec09e15-a4fd-4c2f-b2b4-42e516d0799e

Expected behavior

While we are not currently optimizing for mobile users on studio, the user should still be able to use the mobile keypad to input

Steps to reproduce

Using a mobile device, in the Questions tab, add a new question and use the formula editor to input. Confirm whether (or not) on a touch screen device, the inputs from the touch screen keyboard are input into the "edit" state of the question.

Context

unstable

AI usage

none

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.

Research direction

Start in the Questions tab on a physical mobile device and reproduce the formula editor flow described in the issue. Confirm whether touch-screen keypad input is retained while the question remains in edit state; the issue is done when mobile keypad input works reliably instead of returning the editor to its closed state.

Written by the indexing model from the issue text.

Assessment

Domain
frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.