dsh-mobile-flow
DeepSeek Harness Web UI 的移动端修复：在窄屏（≤720px）上，输入栏和 AI 确认卡片会随页面滚动，而不是固定在视口底部；边缘间距缩小；切换会话时不再自动聚焦输入框；工作区行
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add dsh-mobile-flow@0.7.2Mobile Flow 以 dsh-mobile-flow 发布，当前版本为 0.7.2。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
English | 简体中文
Two mobile fixes for the DeepSeek Harness (dsh) Web UI:
<textarea>, sidestepping the Lexical contenteditable IME flow that swallows text on Android keyboards (voice input most of all).A client-side overlay plus one slot component. No product source is modified; removing the plugin restores the stock behavior exactly.
The stock Web UI pins the composer seat with position: sticky; bottom: 0. That seat hosts not only the input bar but also the interactive cards the AI raises mid-conversation — ask_user_question option cards, approval prompts, plan review. On a phone all of them stay glued to the bottom of the screen, permanently eating a chunk of the viewport while you scroll back through replies.
The stock composer's text surface is a Lexical contenteditable (createEditor + registerPlainText in packages/client/ui-conversation). Android IMEs — voice keyboards above all — drive composition through Chrome's InputConnection → beforeinput("insertCompositionText") recomposition flow, and a framework editor answers those events by writing its own state back into the DOM. The text being composed, and on recomposition text already committed, gets wiped. A native <textarea> is edited by the platform itself and never enters that fight, which is why the same IME behaves in an ordinary textarea comment box.
On viewports ≤720px (the same breakpoint the official question card uses):
/ menu arbitration and the busy-Enter policy), file pastes are forwarded to the official attachment intake, and locked states follow the product's own editability gate.Desktop (wide viewports) is completely unaffected.
The plugin ships a browser half (exports["./client"], declared via dsh.client.platform: "web"), discovered by the client-modules scanner and loaded from the boot manifest.
<style> tag with @media (max-width: 720px) overrides, removed on unload — fully reversible. All selectors target the product's stable data-* attributes (data-composer-seat, data-conversation-scroll, data-phase, data-slot), never CSS-Modules-hashed class names. The sticky-to-static switch is guarded with :not(:has([data-conversation-composer-overlay])) so views that own their composer overlay (e.g. trajectory) keep the official absolute positioning. On engines without :has() the rules degrade safely back to the stock sticky behavior.conversation.input.overlay slot (a session-scope seat inside the composer card) with the standard props it carries (useInput / inputActions). Every keystroke is mirrored into the official input machine (conversation.input.for(ctx).setDraft), while the read side subscribes to the same store's live snapshot — so the send button, placeholder, / trigger pipeline, attachments and draft persistence all keep working, with no stale-render race to clobber fast typing. The Lexical editor keeps its layout box (hidden, never removed) because that box is what sizes the card for the mirrored draft.plain. A claim (a / command picked from the menu, adjudicating, submitting) hands the surface straight back to the stock editor — command tokens and chips are state a plain-text mirror cannot reproduce.dsh web), any recent 0.1.x releasedsh plugin --profile web add dsh-mobile-flow
dsh plugin --profile web add github:imroc/dsh-mobile-flow
Restart dsh web, then refresh the browser page.
The native takeover is on by default on narrow viewports only (≤720px). To override it — for instance to exercise it on a desktop browser:
// Browser console, same origin, persists
localStorage.setItem("dsh-mobile-flow:input", "off"); // never take over
localStorage.setItem("dsh-mobile-flow:input", "on"); // narrow viewports only (default)
localStorage.setItem("dsh-mobile-flow:input", "force"); // take over on any viewport
localStorage.removeItem("dsh-mobile-flow:input"); // back to default
One-shot override: ?dsh-mobile-input=1 (force) / =0 (off).
Diagnostics have their own persisted switch (the tool-row 诊断 button writes it; no URL typing needed):
localStorage.setItem("dsh-mobile-flow:diagnostics", "bench"); // device test bench
localStorage.setItem("dsh-mobile-flow:diagnostics", "debug"); // event panel
localStorage.removeItem("dsh-mobile-flow:diagnostics"); // off
Growth policy (commit by default: resize at commit points only):
localStorage.setItem("dsh-mobile-flow:growth", "live"); // per-keystroke growth (v0.5.2 behaviour, for A/B)
localStorage.setItem("dsh-mobile-flow:growth", "none"); // always the floor height
localStorage.removeItem("dsh-mobile-flow:growth"); // back to default
Open a session on a phone (or a desktop DevTools window narrowed to ≤720px):
[data-mobile-input]). Type with an IME or voice input: text must not be cleared.dsh web so the bundle revision is recomputed — client bundles are served immutable, and a new rev is what guarantees a phone refresh picks up the new code (never make the user clear caches).The first release broke on HarmonyOS 7's built-in browser (ArkWeb): taps rarely opened the keyboard, and only one character could be typed. Both are addressed:
.grow
(position: relative) which comes after our overlay seat in DOM order, so at equal stacking level it painted
(and hit-tested) above the textarea; a document.elementFromPoint probe hit the stock container at 3 of 5 sample
points inside the input box. Fixed with z-index: 5 + an opaque seat background, pointer-events: none on the
hidden row, and a capture-phase pointerdown on the card that focuses the field for taps anywhere inside it.inert + aria-hidden, with a focusin guard for engines without inert);
geometry writes are idempotent and the field declares user-select: text / touch-action: manipulation.v0.5.2 (second round of HarmonyOS feedback): with the takeover on, the keyboard closed after every character. Cause: mirroring the draft on every keystroke re-rendered the composer card and made Lexical rewrite the hidden editor's DOM — a strict engine drops the IME when the editing surface churns. Now:
/ or @ trigger character is typed (the menus need the machine).min-height: 36px docked / 52px hero) and a matching min-height floor is put on the stock row's box, because the absolutely positioned seat cannot make the card grow; it shrinks back after a send clears the draft.contenteditable="false" next to inert + aria-hidden, so the IME can only ever target the textarea; while the field is focused the seat never moves, the hidden scroller is left alone, and geometry is rounded to whole pixels (no sub-pixel style churn).v0.6.0 (third round of HarmonyOS feedback, current): taking the mirror off the typing path was still not
enough — the per-keystroke geometry writes were the trigger. autosize set the field to height: 0px on every
key, read scrollHeight, wrote the height back (the focused editable collapsed once per keystroke), and the seat
re-aligned itself to the card's box. The rule is now absolute: while the field has focus the plugin performs zero
DOM writes.
height: 0px probe is gone); after blur the field grows to its content, keeps the stock row's min-height in
step, and shrinks back when a send clears the draft (the committed send is the only write performed on a focused
field — it follows an explicit user action);v0.6.1 (fourth round, the slash case): on the device only ONE case still dropped the keyboard — a draft
starting with / (how skills are invoked by hand); plain text was already fine. The cause was the plugin's single
per-keystroke exception: TRIGGER.test(fieldValue) asked "does the text contain /", so any draft containing a
slash mirrored the machine on every keystroke after it — re-rendering the composer card, refreshing the command
menu and rewriting the hidden editor's DOM once per character. Now:
compositionstart decides at the end);CHURN while focused lines — app-side mutations (menu, Lexical) under a live IME are logged too, so "our writes"
and "the app re-rendering" can be told apart from a log alone.Known trade-off: the slash menu still opens, but its list may not filter live while you type (the filter reads the machine draft, which is deliberately stale until a commit point). Switch to 「触发符:逐键」 for live filtering, at the cost of the keyboard dropping on that device.
v0.7.0 (fifth round, the slash moment; ✅ confirmed on a HarmonyOS 7 ArkWeb device: plain typing, / commands and continuous input all behave): on the device only a SINGLE keyboard drop remained — the one at the
moment / is typed (everything after it is fine). The device log plus the stock-editor control (typing / there
keeps the keyboard) narrowed the mechanism to one thing: republishing the draft makes the app rewrite the hidden
stock editor's DOM asynchronously (EDITOR childList +1, outside our gesture), and ArkWeb drops the IME when an
editable surface changes from outside the input method. In the stock path that same DOM change IS the user's own
editing, inside the gesture, so nothing drops.
The trigger mirror is now drop focus → land the write → take focus back, entirely inside the keystroke's gesture:
blur() first (IME down), then flushSync (react-dom) so the re-render the write causes — editor rewrite and menu
mount — completes with nothing focused, then focus() to bring the IME back, still inside the gesture.
v0.7.1: the tool row stays clean — everyday it carries only the escape hatch (输入法✓ / 输入法✗); long-press it for 600ms to call out the 诊断 (diagnostics) button, long-press again to put it away. While diagnostics are on, both 诊断 and 复制日志 (copy log) show up by themselves.
v0.7.2 (phone report: tapping the input box after "new session" did nothing): right after a new session is
created its workspace may not be resolved yet — in that window the product's card is not an input at all but the
workspace picker trigger (aria-haspopup="menu", contenteditable="false", no bound editor). The takeover used
to claim it anyway and latched that non-editability into the native textarea's readOnly: tapping the box raised
no keyboard and no caret, the card's own "open the picker" tap was swallowed, so the user could neither type nor pick
a workspace — and it did not recover once the workspace resolved (only a session switch, i.e. a remount, did).
That is exactly the reported "first new session dead, switch away and create another and it works" pattern.
Fixes:
aria-haspopup="menu" (picker trigger) and aria-disabled="true"
(blocked composer / removed session / offline parent). When it is not an input, the takeover stays completely out of
the way: no card marker, no seat, no swallowed tap — the product's own picker tap works.MutationObserver on those two attributes): the moment the workspace resolves
and the composer becomes a real input, the takeover attaches — no latch.contenteditable="false", so any observed "true" is the product
making its composer editable again — the field's readOnly is cleared then, so a latched field can never outlive
the state that caused it.Escape hatch: a small tool-row button (输入法✓ / 输入法✗, narrow viewports only) swaps back to the stock input box and remembers the choice — no device can be left stuck.
Diagnostics (tool-row 诊断 button, or URL ?dsh-mobile-input=bench / ,debug):
height:0
absolute container (the seat's shape), C B plus a style write per keystroke (the pre-0.6 autosize, the
control), D B with logging only (the 0.6 behaviour), E bare textarea inside an iframe (a clean document).
The variant followed by a KEYBOARD ...px line is the guilty one;Verified on a live page: test/probe-live.mjs drives the real app over CDP (390x844) and asserts, among other
things, that typing writes nothing to the page DOM.
@ reference decorations) is not shown; entering a command claim switches back to the stock editor automatically.npm install --no-save jsdom react@18 react-dom@18
node test/takeover.test.mjs # runs the real client bundle in a jsdom composer card
The test boots the shipped lib/client.js, renders the slot entry through React against a
composer-card DOM, and asserts the render path, the draft mirror (typing / IME composition /
machine-side writes), the Enter gesture, and the phase gate that hands the surface back to the
stock editor. It exists because a broken entry renders nothing visible — only a console error.
dsh plugin --profile web remove dsh-mobile-flowdsh.profile.bundles entry, restart dsh weblocalStorage.setItem("dsh-mobile-flow:input", "off") and refresh (turns off the native input only; the layout fixes stay)No product source is modified; upgrades do not overwrite it.
MIT