Strata 0.1.6

Per-editor input appearance

TextField and TextArea accept TextInputAppearance.Custom with normal, focused, and disabled nine-slice images, an insertion-caret color, and a composition-underline color. This supports search fields and message/note editors that blend into light or application-colored panels while using the standard retained editor. Text color and font remain controlled by the existing textStyle and font arguments.

The new overloads preserve all existing signatures, and omitting the appearance retains the previous profile frame and editing decorations. TextInputAppearance.Default explicitly selects that same behavior. Custom transparent pixels reveal the underlying background, and custom nine-slice centers stretch without changing editor padding or text metrics.

Appearance changes repaint the existing editor without remeasuring, replacing input nodes, or discarding focus, composition, or scroll. This is a paint optimization; changing pixels can still require native rasterization and upload. Retain immutable images and appearances outside observed content, and use a narrow Observe for a changing theme. Direct enabled State inputs remain available on every appearance overload.

The shared runtime tests cover default pixel compatibility, transparent frames, invalid borders, caret and composition colors, disabled frames, retained editing state, paint-only changes, and idle-frame reuse. The loaded-client scenario checks retained nodes, phase counts, idle native work, and exact native/headless image agreement through the existing version adapters.

Generated API references and the compiled reactive skill example include the new overloads and appearance selection. See the Strata skill and component reference.

Exact transformed viewport clipping

Fractional scaleToFit geometry now keeps scroll and explicit paint clips precise until final physical pixel coverage is determined. A viewport edge at 43.5 logical pixels therefore clips at physical pixel 174 at density four, rather than admitting two pixels into an adjacent header. Integer geometry and retained frame reuse remain unchanged. Portable images crossing a fractional edge use the bounded fallback without changing their source mapping; images fully inside keep the direct native texture path.

Custom exhaustive display-list backends must handle the new DrawCommand.PushFractionalClip variant, balanced by the existing PopClip. The Minecraft presenter rejects opaque platform payloads crossing fractional clips before frame-layer submission; wholly contained payloads remain supported. Portable standard components require no screen API or layout changes.