Усилить мерцание hero-фона и осветлить текст при наведении#153
Conversation
Adding .gitkeep for PR creation (default mode). This file will be removed when the task is complete. Issue: #152
Working session summaryImplemented and pushed the fix to PR 153: #153 Changed the hero background flicker to use a much wider visible opacity cycle and updated the teaser hover state to use light text on a darker blue pill. Added focused regression tests plus a Playwright hover screenshot in Verification completed:
PR 153 is marked ready for review. GitHub reports no status checks configured for this branch, and the local worktree is clean. This summary was automatically extracted from the AI working session output. |
🤖 Solution Draft LogThis log file contains the complete execution trace of the AI solution draft process. 💰 Cost estimation:
📊 Context and tokens usage:
Total: (127.6K + 4.2M cached) input tokens, 18.4K output tokens, $6.311652 cost 🤖 Models used:
📎 Log file uploaded as Repository (31729KB)Now working session is ended, feel free to review and add any feedback on the solution draft. |
Root cause
PR #151 kept the automatic hero background flicker very subtle: the keyframes only moved between
opacity: 0.12and0.24, so the effect was hard to notice. The active teaser pill also still forced blue text, matching the low-contrast hover state shown in issue #152.Fix
0.08->0.54->0.16->0.46opacity cycle with stronger saturation and brightness peaks.Reproduction and verification
Before the fix, the focused hero tests failed because the flicker opacity never dipped below
0.12or peaked above the new visibility threshold, and the hover state still used a pale-blue pill with blue text.Verified with:
node --test tests/hero-shimmer.test.mjs tests/hero-background.test.mjs npm test npm run buildPlaywright verification:
Автоматизация без программистовand confirmed computed text color isrgb(248, 250, 252)onrgba(37, 99, 235, 0.64).hero-background-flickerwith a9sanimation.Screenshot
Fixes #152