iPad UI issues: Incomplete renders
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- ios
- Domain
- mobile
Research direction
The report bundles several separate iPad rendering problems: notes going invisible while editing, markdown tables not rendering, the floating keyboard breaking layout, and the action bar missing in zoomed block view. The payload names no files, tests or entry points, so the first step is to reproduce on an iPad or emulator and split the report into separate issues. Done would be one narrowed, reproducible problem with a named component.
Written by the indexing model from the issue text.
Description
Search first
- I searched and no similar issues were found
What Happened?
https://github.com/user-attachments/assets/21b01d70-d2e4-4e3f-9b4e-bf700ebcc387
- Editing a block renders rest of the notes invisible
- Markdown tables do not render
- Floating keyboard also causing rendering issues
- Action bar (indent controls etc.) are missing when zoomed into a block
- Black sections on screen with floating keyboard and zoomed in block view
Reproduce the Bug
Zoom into a block for editing to check whether the action bar appears
Open keyboard and set to floating to check for rendering issues
Add a markdown table (or sync one) and it is not rendered as a table
Expected Behavior
No response
Screenshots
No response
Files
No response
Browser, Desktop or Mobile Platform Information
iPad Air M4 running iPad OS 27.0.1
Logseq v2.0.2 (Build 50), Revision 709c3281
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.
- I'm willing to submit a PR (Thank you!)
- Dominant language
- No language data
- Stars
- 29
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from logseq/db-test
-
Web build on a phone: the fold arrow of an h1/h2 block lies on its bullet, so tapping the bullet folds instead of zooming inPossibly taken @tiensonqin claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 87/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
-
Page titles with `$$`, `$&`, `` $` `` or `$'` change when block refs are resolvedPossibly taken @RaphaelFakhri claimed this 19 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
`#Asset` label is not displayed on asset nodes when `Hide from Node` is disabledPossibly taken @tiensonqin claimed this 22 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Similar issues
-
Area-UIUX Issue-Bug Issue-Easy (good first issue)
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
TeamAmaze/AmazeFileManager#4769 ·
Maintainers usually reply within 7 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
GHRik/bielik_oneclick_launcher#36 ·
Maintainers usually reply within 1 day
-
`entitlementVerificationMode` defaults to `DISABLED` and overrides the native default (`INFORMATIONAL`)Possibly taken @AlvaroBrey claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
RevenueCat/react-native-purchases#2127 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
bug good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 78/100