inspector/clients
Repository files (latest commit first)
Filename Latest commit message Latest commit date
cliffhall d49798c91c fix(web): key enlarge carets by Map, and count maxLength in code points
Two more from review, both about field data the schema controls.

The caret record was a bare object keyed by field name, and field names
come from a server's schema. A field legitimately named `constructor` or
`toString` read back an inherited function rather than undefined, so the
documented end-of-value fallback never fired and that value reached
setSelectionRange. Use a Map, which has no such keys.

JSON Schema counts maxLength in Unicode code points; String.length counts
UTF-16 code units. A field holding one emoji measured 2, so a maxLength:2
field with room for another character was treated as full and refused its
newline. Count code points. The maxLength handed to the DOM input still
carries the HTML attribute's own UTF-16 counting; that predates this and
is left alone.

Signed-off-by: cliffhall <cliff@futurescale.com>
2026-08-26 10:23:43 -04:00
..
cli fix(oauth): walk the candidates in the CLI refresh path too 2026-08-26 00:34:27 -04:00
launcher fix: walk contentSchema, await the error envelope, correct the README claim 2026-08-25 03:26:39 -04:00
tui fix: map the new exit code, keep add runnable, distinguish severity by shape 2026-08-25 02:37:10 -04:00
web fix(web): key enlarge carets by Map, and count maxLength in code points 2026-08-26 10:23:43 -04:00