max / quasi

0.20.1: this renderer can press what it draws, and three things could not be pressed The blocker was fonts, not the harness. With `default-features = false` every string measures zero points wide, so a `Response` covers no pixel, is never hovered, and no injected click reaches it however faithfully it is sent. A dev-dependency turning `default_fonts` on applies to this crate's own tests and to nothing a consumer builds, so the dependency keeps the flag it had and no font is committed. With that, `Host` drives a real `Context` a frame at a time and aims the pointer at the shapes the previous frame painted, rather than at arithmetic over the layout. Six tests: a row opens, each row answers for itself, a right-click raises the menu and the item fires its route with the confirmation it was described with, and the same two over a table. They found three defects, all of which the suite could not previously see: A list row's interact id was ("row", value.unwrap_or("")), and `Row::value` is only set by `ticking`, so every row of a list without checkboxes shared one id. egui answers a repeated id with an error label and one shared interaction, so the second row onwards could not be clicked at all. Falls back to the row's position, which is the only thing distinguishing rows that carry no value; the value still wins where there is one, because it survives a reorder. A table row hung both gestures on `ui.response()`, which carries the sense the `Ui` was built with -- `Sense::hover()` -- so `clicked()` and the secondary click `context_menu` reads were permanently false. Neither opening a table row nor raising its menu did anything, in the one consumer whose file list is a `Node::Table`. Now interacts for the sense it needs, as `list_row` already did. `Row::menu` drawing nothing, fixed in 40c7977 by reading. Now asserted. Each was verified by putting it back and watching the intended test fail.