Android Chrome issue with menubuttons
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 16.3k
- Forks
- 2.3k
- PR merge metrics
- No merged PRs in 30d
Description
📝 Provide detailed reproduction steps (if any)
The issue can be reproduced using Chrome on Android by:
- Visiting the inline editor example
- Click on the body text below the image. [Edit: Ensure the Android on-screen keyboard is showing]
- Click on the font selection menubutton
✔️ Expected result
The menubutton menu should open
❌ Actual result
The entire toolbar disappears, as if the editor lost focus. This makes it impossible to use the menubutton.
Note: A similar behavior happens in the non-inline editor; the issue is just more obvious and problematic in the inline editor. In the basic editor, when the focus is inside the editor text, when a menubutton is clicked the first time the editor loses focus and the menu doesn't open. A second click will open the menu.
📃 Other details
- Browser: Chrome 138.0.7204.179
- OS: Android 16 on Pixel 9a
- First affected version: Based on trying the examples for previous version, this issue first appeared in version 7
- Worked in version: It seems to work fine in version 6
If you'd like to see this fixed sooner, add a 👍 reaction to this post.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue in the inline editor example on Chrome for Android with the on-screen keyboard visible, then compare the basic editor behavior. Trace the menubutton focus handling and compare the working version 6 behavior with version 7 and later. Done means the menu opens on the first click and the toolbar remains visible in both inline and non-inline editors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, typescript
- Domain
- frontend, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100