From 5658ac148c7cabfe4908cb2036c5ee85fee807d0 Mon Sep 17 00:00:00 2001 From: Andreas Reinhold / reini Date: Thu, 17 Sep 2026 21:23:47 +0200 Subject: [PATCH] Drop the Tailwind framing from a stale comment in app.css MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The recovery-codes pulse comment still explained itself against Tailwind's animate-pulse, which left the stack in 2.0.0. The reason stands on its own: the package keeps no keyframe utility for a pulse loop, so the loading state animates on the effects spring instead. config/livewire.php:237 stays on Livewire's own "tailwind" default: SealShare still installs livewire-material ^2.0 from Gitea, whose vendor copy has no `pagination::material` view yet, so pointing pagination_theme at it now would break pagination. The package takes the theme over itself once 2.2.0 is tagged and pulled. DesignLanguageTest carried no Tailwind wording to update. Full suite (322) and Pint green, unchanged — run against the old vendor copy, so the guard's new undeclared-class check is not exercised here yet. Co-Authored-By: Claude Opus 5 (1M context) --- resources/css/app.css | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/resources/css/app.css b/resources/css/app.css index c9dc491..8bcdfe0 100644 --- a/resources/css/app.css +++ b/resources/css/app.css @@ -268,7 +268,7 @@ /* * resources/views/pages/settings/two-factor/recovery-codes.blade.php: a code dims to M3's disabled * content opacity while regenerateRecoveryCodes() is in flight, and back, on the effects spring - * instead of Tailwind's animate-pulse loop — 2.0.0 keeps no keyframe utility for it. The + * rather than a keyframe pulse loop — 2.0.0 keeps no keyframe utility for one. The * transition sits on the code itself so the way back eases too; under reduced motion the token's * duration is 0ms. */