Bugzilla

Animated GIFs are already movies, even though they play in `<img>` tags (see also bug 895131, which goes the other direction). I'd like `<img src="animated.gif">` to behave pretty much identically to `<video src="animated.webm" autoplay loop muted>`, by which I mean the context menu should contain Pause, Play Speed, Loop, Show Controls, and Full Screen (the View Video and Copy Video Location are already covered by View Image and Copy Image Location, though we could replace all "Image" references with "Video" if desired).

As animated image formats like [Animated WebP](https://developers.google.com/speed/webp/faq#why_should_i_use_animated_webp), Apple [Live Photo](https://support.apple.com/en-us/HT207310), and Google [Motion Photo](https://ai.googleblog.com/2018/03/behind-motion-photos-technology-in.html)/[Motion Stills](https://get.google.com/motionstills/) get more popular, this line will continue to blur. I like the simplicity of considering movie-like images as images with animated-gif-like defaults (autoplay, loop, muted, no controls), but I really think we need the video context menu and the ability to stop or show controls.

Animated GIFs are already movies, even though they play in `<img>` tags (see also bug 895131, which goes the other direction). I'd like `<img src="animated.gif">` to behave pretty much identically to `<video src="animated.webm" autoplay loop muted>`, by which I mean the context menu should contain Pause, Play Speed, Loop, Show Controls, and Full Screen (the View Video and Copy Video Location are already covered by View Image and Copy Image Location, though we could replace all "Image" references with "Video" if desired).

As animated image formats like [Animated WebP](https://developers.google.com/speed/webp/faq#why_should_i_use_animated_webp), Apple [Live Photo](https://support.apple.com/en-us/HT207310), and Google [Motion Photo](https://ai.googleblog.com/2018/03/behind-motion-photos-technology-in.html)/[Motion Stills](https://get.google.com/motionstills/) get more popular, this line will continue to blur. I like the simplicity of considering movie-like images as images with animated-gif-like defaults (autoplay, loop, muted, no controls), but I really think we need the video context menu and the ability to stop or show controls.

Another thought is how we deal with animated gifs that are set via CSS `background-image`. We already have View Background Image, so we could presumably add most of the video context menu right there (not Show Controls though; where would they appear?).

Animated GIFs are already movies, even though they play in `<img>` tags (see also bug 895131, which goes the other direction). I'd like `<img src="animated.gif">` to behave pretty much identically to `<video src="animated.webm" autoplay loop muted>`, by which I mean the context menu should contain *Pause*, *Play Speed*, *Loop*, *Show Controls*, and *Full Screen* (*View Video* and *Copy Video Location* are already covered by *View Image* and *Copy Image Location*, though we could replace all "Image" references with "Video" if desired).

As animated image formats like [Animated WebP](https://developers.google.com/speed/webp/faq#why_should_i_use_animated_webp), Apple [Live Photo](https://support.apple.com/en-us/HT207310), and Google [Motion Photo](https://ai.googleblog.com/2018/03/behind-motion-photos-technology-in.html)/[Motion Stills](https://get.google.com/motionstills/) get more popular, this line will continue to blur. I like the simplicity of considering movie-like images as images with animated-gif-like defaults (autoplay, loop, muted, no controls), but I really think we need the video context menu and the ability to stop or show controls.

Another thought is how we deal with animated gifs that are set via CSS `background-image`. We already have *View Background Image*, so we could presumably add most of the video context menu right there (not *Show Controls* though; where would they appear?).