Editor keyboard: docked at the bottom, following the writing cursor #79

anas · 2026-10-09T16:15:28Z

anas commented

2026-10-09 16:15:28 +00:00

Owner request: in the moderators' editor, the Urdu keyboard opened under the search box at the top of the page, far from the text being written. It should stay with the writing.

Content editor (the toolbar's keyboard button)

The keyboard is docked at the bottom of the window, centred, like a phone keyboard.
The page follows the writing cursor: when the line being written would go under the keyboard, or above the top of the window, the page scrolls to keep it just above the keyboard. This happens while typing, moving with the arrow keys, clicking another line, or resizing.
The page gets extra room at the bottom while the keyboard is open, so the last couplets can come up above it.
Focus stays in the editor, as before.

All keyboards

A ✕ key closes the keyboard; closing it returns it to the header.

Unchanged: the search box and other boxes keep the keyboard under the search box, and the note dialog keeps it under its box.

First version tried and replaced: a keyboard floating just below the cursor hid the lines underneath it, so a click on them could hit the keyboard instead.

Tested in headless Chrome on a Ghalib ghazal:

the editor keyboard docks at the bottom and focus stays in the editor;
a key types into the line;
scrolled so the cursor's line was behind the keyboard, at four lines down the poem: each time the page brought the line back above the keyboard;
✕ closes it and puts it back in the header;
search still opens the keyboard in the header.
The test draft and account were removed.

Made in a separate worktree from the latest main.

🤖 Generated with Claude Code

Owner request: in the moderators' editor, the Urdu keyboard opened under the search box at the top of the page, far from the text being written. It should stay with the writing. **Content editor** (the toolbar's keyboard button) - The keyboard is **docked at the bottom of the window**, centred, like a phone keyboard. - The page **follows the writing cursor**: when the line being written would go under the keyboard, or above the top of the window, the page scrolls to keep it just above the keyboard. This happens while typing, moving with the arrow keys, clicking another line, or resizing. - The page gets extra room at the bottom while the keyboard is open, so the last couplets can come up above it. - Focus stays in the editor, as before. **All keyboards** - A **✕** key closes the keyboard; closing it returns it to the header. **Unchanged:** the search box and other boxes keep the keyboard under the search box, and the note dialog keeps it under its box. **First version tried and replaced:** a keyboard floating just below the cursor hid the lines underneath it, so a click on them could hit the keyboard instead. **Tested** in headless Chrome on a Ghalib ghazal: - the editor keyboard docks at the bottom and focus stays in the editor; - a key types into the line; - scrolled so the cursor's line was behind the keyboard, at four lines down the poem: each time the page brought the line back above the keyboard; - ✕ closes it and puts it back in the header; - search still opens the keyboard in the header. - The test draft and account were removed. Made in a separate worktree from the latest main. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

anas added 1 commit 2026-10-09 16:15:28 +00:00

Editor keyboard: docked at the bottom of the window and the page keeps the writing line above it; a close key; search keeps the header keyboard 6a62df9ee0

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

anas merged commit dd5771a128 into main

2026-10-09 16:18:36 +00:00

anas referenced this issue from a commit

2026-10-09 16:18:37 +00:00

Merge pull request 'Editor keyboard: docked at the bottom, following the writing cursor' (#79) from feature/floating-keyboard into main

Sign in to join this conversation.

No reviewers

No Label

No Milestone

No project

No Assignees

1 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: anas/divan#79