The screenshot was lying about the app
A screenshot showed a sidebar highlight stuck on the wrong item, even though the page was right, because the picture had frozen a transition that would never finish.
The setup
The Hub is a single HTML file, rendered by WKWebView on macOS and WebView2 on Windows, and both builds take their own screenshot with a --shot flag, because system tools can't reliably capture an out-of-process web view.
The symptom
Clicking Extensions showed the Extensions page, but with the highlight still on Dashboard, which looks like a selector on aria-current that never re-evaluated.
Asking the page instead of the pixels
After a real click and a long wait, the computed styles showed the attributes were correct, but both buttons sat exactly on their starting colours, so they weren't stale, they had simply never started. Adding one line that disabled transitions fixed the picture.
Since the window is never shown on a screen, the engine has no reason to advance an animation, which means the screenshot was an accurate picture of a moment that was never going to move on.
What changed
The page itself was left alone. The real near-miss was almost shipping a workaround with a confident comment about a WebKit bug that doesn't exist. Instead, the shot flag now disables transitions and animations before it does anything else, and it gained --shot-delay for flows that sign in and download first.
So the general rule is that before believing a diagnosis, you should change one variable that should be irrelevant, because if that fixes the bug, the bug was somewhere else.
This is a shorter version of a post on the Pioneering blog, so if you want the full story, read the original on pioneering.app.
Next postA repository isn't a payload
