Repository navigation
Conversation
commit: |
cowboyd
force-pushed
the
tree-input
branch
2 times, most recently
from
August 22, 2026 05:24
0afad40 to
a349bca
Compare
Contributor
Author
|
closing out in favor of a DOM based substrate. See #37 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
An editable input is the first element that exercises the complete interactive architecture rather than only one layer. It must become focusable when attached, receive key events through the focused dispatch path, maintain semantic editing state, participate in layout, request frames through Host mutations, and emit typed changes to raw or framework consumers. Building it from the APIs already introduced demonstrates that interactive elements can be authored as composable extensions instead of privileged core cases.
Editing behavior lives in
InputApi, independent of any particular framework. The model uses code-point positions rather than UTF-16 code units, normalizes pasted line breaks for a single-line control, and keeps key-repeat behavior input-specific. Emittinginputonly when the value changes gives every adapter the same predictableonInputsemantics.This PR adds the typed
inputelement and semantic insert, delete, and caret movement operations. It composes focus, keyboard handling, layout, and typed input events while exposing the current value and caret through element properties. Tests cover editing boundaries, multi-code-unit characters, key mappings, repeats, delegation, and event emission.