0.53.0: carry makeover-webview 0.60.0, which draws a wait
`awaiting_rules` is new there, and every consumer of the design system
takes its CSS through this crate. A consumer left on 0.59 links a
stylesheet that still says nothing about `[data-awaiting]`, which is the
state phase 2 of wiki `loading-and-progress-standard` exists to end.
The generated sheet already carried `--cadence-activity` from
makeover-timing 0.1.1, so the blink resolves the moment the rules arrive
and the reduced-motion block that zeroes it comes along unchanged.
Author: Max Johnson <me@maxj.phd> · 2026-08-26 19:56 UTC
description = "Build-script support for the make-family design system: materialise makeover's themes and makeover-webview's stylesheet into a Tauri app's frontend, once, instead of copying the same twenty lines into every consumer's build.rs."
6
6
license = "MIT"
@@ -37,7 +37,7 @@
37
37
# a cell into a run of leaves, so "this text is a link" became a member the run
38
38
# holds rather than a field on one container, and the renderer needed a name for
39
39
# it that was not invented locally.
40
-
makeover-webview = "0.59.1"
40
+
makeover-webview = "0.60.0"
41
41
makeover-geometry = "0.7"
42
42
# 0.1.1, not 0.1.0: the cadence axis and `reduced_motion_css` are what
43
43
# `timing_css` emits, and 0.1.0 has neither. A consumer resolving 0.1.0 would