max / makeover-touch

Release 0.31.2: drop citations to files that no longer exist The census argument pointed at goingson and Balanced Breakfast `frontend/js/touch.js`, and Affordance::Haptic pointed at goingson `frontend/js/haptics.js`. All three went with the JS in the quasi port, so the docs cited paths a reader cannot open. The argument they supported is unchanged and kept: Gesture and Haptic adapt behaviour, no stylesheet contains behaviour, so a media-query census could never have found them. The line of JavaScript that was the evidence stays; only the dead paths go. Haptic now says plainly that it has no consumer at present, which is true since goingson@2988cd6 stripped the stranded plugin.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DwpiantpUgohzML4xr6KeQ

Author: Max Johnson <me@maxj.phd> · 2026-08-31 14:39 UTC

Signed with PGP, not checked

Commit: 11a19c0494a445ec2b8d95f9fda6587f4bdd5fd1

Parent: 675a64b

2 files changed, +9 insertions, -8 deletions

M Cargo.toml +1 -1

			@@ -1,6 +1,6 @@
1	1		[package]
2	2		name = "makeover-touch"
3		-	version = "0.31.1"
	3	+	version = "0.31.2"
4	4		edition = "2024"
5	5		description = "The adaptation layer of the make-family design system: which affordances exist at a given input class and window size class. Names what appears and disappears, never how much space it takes."
6	6		license = "MIT"

M src/lib.rs +8 -7

			@@ -37,16 +37,16 @@
37	37		//! Two of the eight members are not in that census at all, and the exception is
38	38		//! worth stating rather than leaving to be noticed. [`Affordance::Gesture`] and
39	39		//! [`Affordance::Haptic`] adapt behaviour, which no stylesheet contains, so
40		-	//! counting `@media` blocks could never have found them. Their evidence has the
41		-	//! same shape in a different file: goingson `frontend/js/touch.js:12` and
42		-	//! Balanced Breakfast `frontend/js/touch.js:12` carry the identical line
	40	+	//! counting `@media` blocks could never have found them. Their evidence was a
	41	+	//! line of JavaScript rather than a media query:
43	42		//!
44	43		//! ```js
45	44		//! const isTouchDevice = ('ontouchstart' in window) \|\| (navigator.maxTouchPoints > 0);
46	45		//! ```
47	46		//!
48		-	//! and each hangs five gestures off it. Two apps, arrived at independently,
49		-	//! hand-rolling the density question this crate exists to answer.
	47	+	//! which two apps carried identically, each hanging five gestures off it. Two
	48	+	//! codebases arriving independently at the density question this crate exists
	49	+	//! to answer, and neither able to state it where a stylesheet could see it.
50	50		//!
51	51		//! # The two axes are borrowed, never redefined
52	52		//!
			@@ -204,8 +204,9 @@
204	204		/// tick as a drag crosses a threshold, the thump as a gesture fires.
205	205		///
206	206		/// A contact-patch claim, which is what makes it this crate's business
207		-	/// despite being the one member nothing on screen shows. goingson
208		-	/// `frontend/js/haptics.js`.
	207	+	/// despite being the one member nothing on screen shows, and the one with
	208	+	/// no consumer at present: the renderers that would deliver it do not ask
	209	+	/// for it yet.
209	210		///
210	211		/// The proxy breaks where the hardware has haptics and the user or the OS
211	212		/// has switched them off. That is neither [`Density`] nor [`SizeClass`], and