mirror of
https://github.com/screentinker/screentinker.git
synced 2026-08-14 14:23:14 -06:00
702e107972
The directory-search widget draws its own on-screen keyboard, on by default, sized and themed to the panel. On Android it was never visible: the page autofocuses a real <input>, which is the signal to raise the system IME, and that lands over the bottom of the screen — exactly where our keyboard is. So a directory panel showed Google's keyboard instead of the one the widget ships: split across a 1920x1080 screen, with mic, GIF, emoji, clipboard and a settings key that opens Google's own UI on a kiosk. On the panel that turned this up, the system keyboard WAS voice input — the only enabled IME was Google's voice IME, so touching the search box opened a microphone, on a wall-mounted tenant directory. When we draw a keyboard, the input now carries inputmode="none", so the platform leaves its keyboard down. The buttons write input.value directly, so nothing about typing changes. Browsers that don't know inputmode ignore it, which is the right fallback — a desktop preview behaves exactly as before. Gated on the flag, not applied to the markup: with show_onscreen_keyboard off there is nothing to cover, and the platform keyboard is the only way left to type. Verified by removing the line and watching the new guard fail. 1669/1669 pass. |
||
|---|---|---|
| .. | ||
| config | ||
| db | ||
| lib | ||
| middleware | ||
| player | ||
| routes | ||
| scripts | ||
| services | ||
| test | ||
| ws | ||
| .gitignore | ||
| config.js | ||
| package-lock.json | ||
| package.json | ||
| server.js | ||
| smoke-ui.js | ||
| version.js | ||