It appears that Tumblr has changed the GIF-displaying code to no longer display a stationary poster element, then hide it once the animated GIF it is for has been loaded. Instead, they're swapped (or something; I can't quite tell) using javascript. Presumably whoever made this change ensured that there will be no flickering effect on image load when this happens...? I hope?
This breaks the XKit code, added in #1853, which a) makes disabling most GIFs quite a bit faster and more efficient and b) adds a feature to not download them until they're hovered over. Disable GIFs still works, though (using our old canvas-based code path that was used before this change for webp images).
I don't currently have any ideas how to keep the "don't download" feature if Tumblr keeps this change, but I'm leaving it in the issue title because, like, idk, never say never.
I think it probably makes sense to not assign or helpwanted this issue and let the stale bot serve as an automatic remindme. We should at least see if the change is an a/b or a mistake or something (it hasn't been announced in changes yet).
It appears that Tumblr has changed the GIF-displaying code to no longer display a stationary poster element, then hide it once the animated GIF it is for has been loaded. Instead, they're swapped (or something; I can't quite tell) using javascript. Presumably whoever made this change ensured that there will be no flickering effect on image load when this happens...? I hope?
This breaks the XKit code, added in #1853, which a) makes disabling most GIFs quite a bit faster and more efficient and b) adds a feature to not download them until they're hovered over. Disable GIFs still works, though (using our old canvas-based code path that was used before this change for webp images).
I don't currently have any ideas how to keep the "don't download" feature if Tumblr keeps this change, but I'm leaving it in the issue title because, like, idk, never say never.
I think it probably makes sense to not assign or helpwanted this issue and let the stale bot serve as an automatic remindme. We should at least see if the change is an a/b or a mistake or something (it hasn't been announced in changes yet).