aboutsummaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorTianren Dong <tianrendong.dtr@gmail.com>2026-09-10 09:58:32 -0400
committerGitHub <noreply@github.com>2026-09-10 09:58:32 -0400
commit304c40a7d42b3c8ad8e93627012c53b086c72065 (patch)
tree0c63797b791ffed2ef94f174d6cedbe7898dd75d /README.md
parentf746631041e15e0c71d464d830ca2df7603f1476 (diff)
parentec23b553a245d3d57f428d03002ed77a785d300a (diff)
Merge pull request #14 from tianrendong/fix/input-reliability
Improve Chrome input reliability and release 0.15.49
Diffstat (limited to 'README.md')
-rw-r--r--README.md6
1 files changed, 6 insertions, 0 deletions
diff --git a/README.md b/README.md
index 094dfe6..a6774bc 100644
--- a/README.md
+++ b/README.md
@@ -74,6 +74,12 @@ Second doctor run should show all checks passing.
Tool parameters and gotchas are documented inline in Pi.
+### Typing into rich editors
+
+`chrome_type` and `chrome_fill` use one native CDP `Input.insertText` operation for focused contenteditables. This avoids per-character delays for long text and preserves Unicode/newlines. Ordinary inputs and textareas retain individual key events.
+
+For an editor that needs a `keydown` for every character, pass `perCharacter:true`. Bulk insertion still uses Chrome's input system, but does not emit per-character key events or a clipboard `paste` event. Use `includeSnapshot:true` to verify the result; `chrome_fill` still honors `domFallback:false` when synthetic fallback is unwanted.
+
---
## Safety model