I’ve been reloading them off and on, and just now replicated the problem by loading the lazy page (worked) then the non-lazy page (failed):
Unfortunately, Firefox seemed to completely reload assets on reload (Disable Cache is not set) with devtools open, but… this is odd:
The user seems to have changed/updated their avatar, and we redirected to the new one? I’m not sure what triggers this @david.
I’d hazard a guess this additional redirect briefly triggered the Firefox bug. Which is in line with the difference in behaviour due to the redirect chaser.
Maybe I can trigger it?
I changed my avatar, let’s see if it breaks when I reload in an hour.
EDIT: eh, it didn’t break this time
but my shenanigans on this page seem to be poorly affecting other pages… NONE of these avatars are working now and I think it’s because a network request is “stuck”.
