Floating keyboard on iPadOS moves actions bar around (Screen recording attached)
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- ios
- Domain
- frontend
Research direction
Start by reproducing the floating keyboard behavior on an iPad using the steps in the issue, then inspect the UI entry points for the bottom action bar and graph settings menu. The issue names no files or tests, so locate those components from the app’s navigation and keyboard handling. Done means the action bar stays fixed while the floating keyboard moves and global settings remain accessible across graphs.
Written by the indexing model from the issue text.
Description
Search first
- I searched and no similar issues were found
What Happened?
When trying to input content using Apple Pencil or the floating keyboard, the bottom action bar jumps around making text entry difficult.
The settings menu is not selectable from another graph (as seen in the end of the video)
Reproduce the Bug
Text entry:
- Select a blank node for entry
- Switch to floating keyboard if not already selected
- Move floating keyboard around
Settings menu:
- Switch graph
- Gear icon appears
- Switch to another graph
- Gear icon replaced by ellipses icon with graph selection menu but no global settings
Expected Behavior
UI elements should be fixed when floating keyboard is active
Global settings should be accessible across different graphs
Screenshots
https://github.com/user-attachments/assets/775abe10-28d7-44e1-b64d-27c6d3175cda
Files
No response
Browser, Desktop or Mobile Platform Information
Logseq 2.0.2 (38) on iPad Air M4 (iPadOS 27)
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
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug sharing & sync
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
navikt/pensjonskalkulator-frontend-monorepo#270 ·
Maintainers usually reply within 1 day
-
reproduced
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
anomalyco/opencode#62873 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
inveniosoftware/invenio-app-rdm#3630 ·
Maintainers usually reply within 2 days