Why. Owner, on production in Chrome: "the loading animation is super weird on chrome..." He did not say which one; find it rather than guess.
What. Open the forge's pages in Chrome (desktop, current stable) and record every loading state: the page-transition bar, skeletons, spinners, the "Setting up…" and "Waking up" pages, live-region swaps. Compare each with Safari and Firefox. Fix what differs or misbehaves in Chrome (likely candidates: a view-transition or @starting-style animation Chrome runs differently, an animation restarted by a live swap, a stuck or double indicator, a flash of unstyled content on navigation). Reduced-motion is respected. Say in the pull which animation it was and what was wrong, with a before and after capture.
Acceptance. A browser test in Chromium loads three pages by navigation and one live swap and asserts one indicator at a time, that it ends, and no layout shift above the budget. The owner looks at the preview in Chrome before it lands.
Why. Owner, on production in Chrome: "the loading animation is super weird on chrome..." He did not say which one; find it rather than guess.
What. Open the forge's pages in Chrome (desktop, current stable) and record every loading state: the page-transition bar, skeletons, spinners, the "Setting up…" and "Waking up" pages, live-region swaps. Compare each with Safari and Firefox. Fix what differs or misbehaves in Chrome (likely candidates: a view-transition or
@starting-styleanimation Chrome runs differently, an animation restarted by a live swap, a stuck or double indicator, a flash of unstyled content on navigation). Reduced-motion is respected. Say in the pull which animation it was and what was wrong, with a before and after capture.Acceptance. A browser test in Chromium loads three pages by navigation and one live swap and asserts one indicator at a time, that it ends, and no layout shift above the budget. The owner looks at the preview in Chrome before it lands.