main
tag: v0.1.0
tag: v0.10.0
tag: v0.11.0
tag: v0.12.0
tag: v0.13.0
tag: v0.14.0
tag: v0.15.0
tag: v0.16.0
tag: v0.16.1
tag: v0.17.0
tag: v0.17.1
tag: v0.18.0
tag: v0.19.0
tag: v0.2.0
tag: v0.20.0
tag: v0.21.0
tag: v0.21.1
tag: v0.22.0
tag: v0.22.1
tag: v0.23.0
tag: v0.24.0
tag: v0.25.0
tag: v0.25.1
tag: v0.26.0
tag: v0.27.0
tag: v0.28.0
tag: v0.29.0
tag: v0.3.0
tag: v0.30.0
tag: v0.30.1
tag: v0.31.0
tag: v0.32.0
tag: v0.33.0
tag: v0.34.0
tag: v0.35.0
tag: v0.35.1
tag: v0.36.0
tag: v0.37.0
tag: v0.38.0
tag: v0.39.0
tag: v0.4.0
tag: v0.40.0
tag: v0.41.0
tag: v0.42.0
tag: v0.43.0
tag: v0.44.0
tag: v0.45.0
tag: v0.46.0
tag: v0.47.0
tag: v0.48.0
tag: v0.49.0
tag: v0.5.0
tag: v0.5.1
tag: v0.51.0
tag: v0.52.0
tag: v0.54.0
tag: v0.55.0
tag: v0.57.0
tag: v0.58.0
tag: v0.59.0
tag: v0.59.1
tag: v0.59.2
tag: v0.6.0
tag: v0.60.0
tag: v0.61.0
tag: v0.62.0
tag: v0.63.0
tag: v0.64.0
tag: v0.65.0
tag: v0.66.0
tag: v0.67.0
tag: v0.68.0
tag: v0.69.0
tag: v0.7.0
tag: v0.70.0
tag: v0.70.1
tag: v0.70.2
tag: v0.71.0
tag: v0.72.0
tag: v0.73.0
tag: v0.74.0
tag: v0.74.2
tag: v0.75.0
tag: v0.75.1
tag: v0.8.0
tag: v0.9.0
tag: v0.9.1
Files
Commits
Tags
Notes
Issues
0.59.1: FIELD_CLASSES holds what this module emits, not what it rules
The three suggestion classes are ruled here and emitted by quasi-webview,
so a list of what this module can put in markup does not hold them. They
reach the vocabulary through the generated sheet, unchanged.
Co-Authored-By
Claude Opus 5 (1M context) <noreply@anthropic.com>
2 files changed,
+8 insertions,
-4 deletions
1
1
[package]
2
2
name = "makeover-webview"
3
-
version = "0.59.0"
3
+
version = "0.59.1"
4
4
edition = "2024"
5
5
# One copy of this renderer per dependency graph, enforced by cargo rather than
6
6
# by remembering. Two versions means the generated stylesheet and the emitted
73
73
"form-option-reason",
74
74
"form-radio-group",
75
75
"form-radio-label",
76
-
"form-suggestion",
77
-
"form-suggestion-detail",
78
-
"form-suggestions",
79
76
"form-unit",
80
77
];
81
78
79
+
// `form-suggestions`, `form-suggestion` and `form-suggestion-detail` are
80
+
// deliberately absent: [`suggestion_rules`] writes their look and
81
+
// `quasi-webview` writes their markup, because a suggestion source is a route
82
+
// and no description layer carries one. They reach the vocabulary through the
83
+
// generated sheet, which is where a name this crate rules but does not emit
84
+
// belongs.
85
+
82
86
/// The state classes a field carries, which take no prefix.
83
87
///
84
88
/// `chosen` and `latched`'s convention, stated in