logseq / logseq/db-test

Android: Text stretched when opening overlay

Open
#1,007 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
No language data
Stars
28
Forks
2
PR merge metrics
No merged PRs in 30d

Description

### Search first

- [x] I searched and no similar issues were found

### What Happened?

When i open an overlay (or how is it called?), the text get stretched.

### Reproduce the Bug

1. Tip a line to start editing text
2. Open sync status or settings overlay

It does not happen without the first step.

### Expected Behavior

Text rendering not getting messed up.

### Screenshots

Image

Image

### Files

_No response_

### Browser, Desktop or Mobile Platform Information

Xiaomi Mi 11 Pro, MIUI 14, Android 13
Logseq Android 2.0.1 (Beta)

### Additional Context

This is not a new issue. I only now figured out how to reproduce it reliably.

### Are you willing to submit a PR? If you know how to fix the bug.

- [ ] I'm willing to submit a PR (Thank you!)

Contributor guide

No contributing guide indexed for this repository

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 by reproducing the issue on the reported Xiaomi device or an Android 13 environment: edit a line, then open the sync status or settings overlay. Trace the Android text-editing and overlay entry points, and compare behavior with and without the editing step. Done means text remains normally rendered when either overlay opens after editing.

Written by the indexing model from the issue text.

Assessment

Tech stack
android
Domain
mobile
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.