3 ms·
That is how my browser behaves normally in Chrome at least. Progressive loading of normal .gifs, playing frames as they are available
by bentpins 9y ago
That is how my browser behaves normally in Chrome at least. Progressive loading of normal .gifs, playing frames as they are available
- nkkollaw 9y agoSure, but the animation sucks. Extremely choppy and slowed down. I wonder if this technique can optimize preloading. For instance, we could send out only 1/2 of the frames (of course, with twice the delay to keep the same animation speed), then load the rest as it's available. I have no idea what I'm talking about yet, but there seem to be something here.
- soneca 9y agoI would prefer, as UX, that it would follow this order: - First load first frame on lowres (may be so lo that is blurred) - Then add a small rotating loading icon on top of image, possibly with a notation that is a GIF - Then load first frame completely at correct resolution - Then load all the other frames in the background, only showing me the first frame still - When all frames are completely loaded, remove loading rotating icon and run the GIF normally.
- nkkollaw 9y agoAwesome suggestions. I'll try to see if it's possible.
- mnutt 9y agoIt seems like this is the same as with video, where the client is trying to determine how many frames it needs to precache before it starts displaying. I'm not sure how much measurement capacity the server has, here?
- pbhjpbhj 9y agoSame for me FF54 on Kubuntu. Sometimes it gets stuck and doesn't show the whole gif but I just assume that's my/the website's connection.