9f8bf98a946fce2a61d2a5bb489cca3e6ca33dc3
Did a real browser QA pass against the deployed site (Playwright, not just isolated HTML harnesses) and found two actual bugs the harness-based checks couldn't catch: - FloatingBg/Sparkles are `position: fixed` full-viewport layers with z-index: 1, while page content like .pony-card only has z-index: auto. Per CSS stacking rules a positioned z-index:1 sibling paints above z-index:auto content regardless of DOM order, so the floating ponies were rendering on top of / poking through the theme-select cards. Changed both to z-index: -1 so they reliably sit behind all normal content. - COLOR_OPTIONS' hue-rotate values were tuned against the wrong baseline hue: base.png's actual body hue is ~0deg (red), but e.g. "Blå" (blue) used hue-rotate(150deg), landing on ~150deg = green, and "Lilla" (purple) used 220deg, landing on ~220deg = blue. Recalibrated all rotations against the real measured base hue so picking a color now actually produces that color on the body. Verified before/after with a side-by-side render of all 8 colors, then confirmed live against the deployed site (clicking "Kropsfarve: Blå" now visibly turns the body blue, not green). 67/67 tests still passing. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
test: 37 frontend tests (App integration, API service, achievements), 43 backend tests — all passing
Description
No description provided
Languages
Python
54.5%
JavaScript
33.3%
CSS
10.2%
HTML
1.9%