Aha -- if I load the testcase in Chrome with their Network DevTools panel configured to "disable cache: checked" and with the throttling dropdown set to "Slow 3G", then they sometimes play the transition on `body` just as Firefox does. (I didn't manage to get them to match Firefox on the original in-the-wild https://2022.internethealthreport.org/facts/ page (i.e. I never saw Chrome play a fade-out animation at pageload there) -- but I also didn't try for very long.) So this interop issue seems to just be a race condition in Chrome, perhaps. (Where they sometimes match us vs. sometimes do something else depending on load ordering.) I'll call this INVALID since it seems like we're internally consistent at least. :) Though perhaps this merits further investigation if anyone's interested.
Bug 1780102 Comment 2 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Aha -- if I load the testcase in Chrome with their Network DevTools panel configured to "disable cache: checked" and with the throttling dropdown set to "Slow 3G", then they sometimes play the transition on `body` just as Firefox does (in testcase 1 and testcase 2). (I didn't manage to get them to match Firefox on the original in-the-wild https://2022.internethealthreport.org/facts/ page (i.e. I never saw Chrome play a fade-out animation at pageload there) -- but I also didn't try for very long.) So this interop issue seems to just be a race condition in Chrome, perhaps. (Where they sometimes match us vs. sometimes do something else depending on load ordering.) I'll call this INVALID since it seems like we're internally consistent at least. :) Though perhaps this merits further investigation if anyone's interested.