diff options
| author | Tianren Dong <tianrendong.dtr@gmail.com> | 2026-05-14 22:46:31 -0400 |
|---|---|---|
| committer | Tianren Dong <tianrendong.dtr@gmail.com> | 2026-05-14 22:46:31 -0400 |
| commit | 58e86b70a0c7f6bf8e44f8b658e8194444ade943 (patch) | |
| tree | b56f638493c4967544b39c465596dddac1d1b4a9 /docs/EXAMPLES.md | |
| parent | 1ec189f8f7f137555e8ae90d6753ee226eefa457 (diff) | |
Audit pi-chrome docs
Diffstat (limited to 'docs/EXAMPLES.md')
| -rw-r--r-- | docs/EXAMPLES.md | 8 |
1 files changed, 3 insertions, 5 deletions
diff --git a/docs/EXAMPLES.md b/docs/EXAMPLES.md index a5cccf4..b3c6286 100644 --- a/docs/EXAMPLES.md +++ b/docs/EXAMPLES.md @@ -119,10 +119,8 @@ On my staging app: ### React controlled inputs ```text -chrome_fill (not chrome_type) for React inputs — it uses the -framework-aware native value setter so the form's state actually updates. -After each fill, the result envelope's valueMatches=true confirms the -component re-rendered with the new value. +Use `chrome_fill` for React inputs when you want to replace the full value. +Pass `includeSnapshot=true` to verify the component re-rendered with the new value. ``` ### File upload without the native picker @@ -160,7 +158,7 @@ Interactive tools use Chrome's real input layer by default: clicks, typing, fill - sign-in flows - guarded buttons - audio/video controls -- fullscreen / permission prompts +- fullscreen and other user-activation checks - pages with strict CSP or user-activation checks Chrome may show its debugger banner while pi-chrome is attached. |