Skip to main content

max / makeover-webview

Correct the header's deletion claim against the measurement
Author: Max Johnson <me@maxj.phd> · 2026-07-31 03:40 UTC
Signed with PGP, not checked
Commit: 3c6ddc271b5465369b58d4f0412c45399b5e358e
Parent: ab536fb
1 file changed, +10 insertions, -3 deletions
M src/lib.rs +10 -3
@@ -18,9 +18,16 @@
18 18 //! # Phase A: the stylesheet
19 19 //!
20 20 //! This module emits component CSS and no markup, deliberately. GoingsOn has
21 - //! 145 `innerHTML` sites and Balanced Breakfast 175 `createElement` sites;
22 - //! moving markup is a migration, while adopting a generated stylesheet is a
23 - //! deletion. The apps keep every line of their markup and gain the classes.
21 + //! 145 `innerHTML` sites and Balanced Breakfast 175 `createElement` sites, so
22 + //! moving markup is a migration where adopting a generated stylesheet is not.
23 + //! The apps keep every line of their markup and gain the classes.
24 + //!
25 + //! It is not a deletion either, which this header claimed until the measurement
26 + //! came in. Adoption across goingson removed 49 declarations net and *added* 25
27 + //! lines: a rule loses its depth declarations and gains a variant selector next
28 + //! to it, so the file stays the same size. What phase A moves is where depth is
29 + //! defined, not how much CSS exists. Numbers and method in the wiki note under
30 + //! "The deletion test, run".
24 31 //!
25 32 //! The bevel properties are byte-identical to what both apps already
26 33 //! hand-write, which is asserted below.