Yep, that's definitely a browser thing - my best guess is that Chrome ignores rendering anything that's opacity: 0 and since your images NEVER rendered even one time initially, the browser didn't even bother to rasterize the image data (probably a performance optimization in Chrome) but then the very first time the browser does have to render it, it is forced to do all that decoding/rasterizing work to create that graphics layer. It's not exactly a cheap process, so it bogs down initially but on
    • Like
    4