0.14.0: take makeover-touch 0.3
Breaking for the same structural reason every bump here is: this crate takes
makeover-touch and makeover-geometry, and Affordance::available accepts
geometry's Density. A consumer resolving touch 0.2 alongside this crate on
0.3 gets two incompatible copies of Density, so the pin cannot lag behind a
touch minor even when nothing here changes.
Nothing here does change. makeover-touch 0.3.0 adds Gesture and Haptic,
which are touch-gained affordances describing behaviour rather than style,
and this renderer emits CSS -- it has nothing to say about either. The one
member it reads is still Hover, and hover_condition() is untouched.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
Author: Max Johnson <me@maxj.phd> · 2026-08-04 13:51 UTC
description = "The webview renderer for makeover-layout. Emits CSS, and is the one renderer that needs no palette: var() is the late binding, so resolution stays with the browser."
6
6
license = "MIT"
@@ -11,7 +11,7 @@
11
11
# The capability axis. `makeover-touch` decides whether a hover rule should be
12
12
# gated at all; `makeover-geometry` spells the gate as a media condition. Both
13
13
# answers are owned elsewhere and neither is re-derived here.