-
Name app-level chrome and the screen drawn over another
-
Let each renderer decide focus, and delete the machinery that argued
-
Take the makeover 0.18.0 cascade
-
Read the share and the measure off the description
-
State the major each consumer is written against on cross-repo git deps
-
Take what moved out to makeover, and name the trait for what it does
-
A cell is an inline run, and the model found two members while it moved
-
Take makeover-webview 0.31.0, where the caret owns its own gap
-
Take makeover-webview 0.30.1, which reads a stylesheet by property
-
Every class this renderer emits is makeover's or declared as its own
-
Take the makeover suite that cannot be doubled
-
Emit the selector classes makeover styles, and check the whole vocabulary
-
Take makeover-layout 0.15.0 and makeover-webview 0.26.0
-
A table cell names its parts in the shared vocabulary rather than in ours
-
A figure carries how its value moved
-
Emit the class names makeover actually defines
-
Markdown is standard: docengine is not a feature
-
Take the current makeover suite
-
Take makeover-webview 0.21.1, so one makeover-geometry resolves
-
Take makeover 0.12: stand-ins, confirm and undo, row menus, paging, sort, keys
-
Take makeover 0.11: a figure strip, a proportion in a row, field constraints
-
A control can write when its value changes, and prose can be markdown
-
Describe a proportion, through makeover's emitter
-
Pin the makeover crates to the versions this code needs
-
Add quasi-webview: a screen description in, an htmx document out