160678 - [RFE]Option to stop animated images (on site-by-site basis)

Status: NEW

(Core :: Graphics: Image Blocking, enhancement, P3)

Description

[Jason Price]

Mozilla has the wonderful "Block images from this server" option.  I'd like
another one right next to it.

I wish I could right click on an animated image, and select "Stop animated image".

I don't want to turn them all off (which there is an option for).  I just want
to stop the hyper annoying ones.

Thanks;
Jason

Comment 1

[Jason Price]

Note: This might be (well, probably is) attached to the wrong component... I
couldn't find a better one.  :-(

Comment 2

[jhacker]

Isn't 'Preferences/Privacy/Images/Loop images' enough for you?
(Okay, I remember earlier netscape version to stop animated gifs
 when pressing the stop button, but ...)

Comment 3

[Jason Price]

No, the preferences, while very nice, are a global change.  I just want to stop
the  images that are REALLY annoying, on a case by case basis.

I can block those ad servers, but I don't like doing that, since advertising is
how some sites stay in business.

Comment 4

[Alfonso Martinez]

*** This bug has been marked as a duplicate of 70030 ***

Comment 5

[Marcus Campbell]

Verified.

Comment 6

[Wesha]

*** Bug 162839 has been marked as a duplicate of this bug. ***

Comment 7

[Wesha]

Guys, this one is NOT a dupe og bug 70030. That bug deals with ALL animated
images at once, and this one requires a context menu item for a _single_ image.
Rather dependency than dupe.

==> REOPEN

Comment 8

[Brodie]

I would like to see this option too, but extended to be a toggle between started
and stopped behaviour. When showing the context menu over an animated image...

1) If it is animated (displaying the animation), include the option "Stop Image
Animation" in the context menu, which when selected stops the animation.

2) If it is not animated, include the option "Show Image Animation" in the
context menu, which when selected starts the animation.

Comment 9

[Marcus Campbell]

The image context menu is already pretty long (that's not even considering
linked images). I'm not sure the UI people, who are more often than not trying
to shorten any menus down, are going to go for something like this. I'd say bug
70030 stands a much better chance at getting fixed and, if it does, it would
likely reduce any chances of this bug being considered.

Comment 10

[Brodie]

>The image context menu is already pretty long

Perhaps this is true, but it need not exclude functionality which is useful, as there are other ways around just adding an item to a long list. Eg move less commonly used functionality to a submenu. Or perhaps even by doing it like Opera, and using a 'quick preference' menu.

The reason I feel this is useful and timesaving, is that for people who browse with 'show animations' set to 'only once' or 'not at all', there is no way to force a particular image on the page to animate without a long and painful process of...
* going into preferences
* finding the image setting and changing it to 'show all animations'
* reloading the page
* looking at the pretty animation
* then the preferences again to turn it off.

It's pretty painful, especially compared to something like Opera which allows you to turn it on and off very easily.

Brodie.

Comment 11

[Jo Hermans]

*** Bug 85621 has been marked as a duplicate of this bug. ***

Comment 12

[Mitchell Stoltz (not reading bugmail)]

Mass reassigning of Image manager bugs to [e-mail], and futuring.
Most of these bugs are enhancement requests or are otherwise low priority at
this time.

Comment 13

[Serge Delbono]

Or just add a simple command to stop animated GIFs. For example as in IE, the
"stop" button stops animations.

Comment 14

[Morten Poulsen]

No, my idea (Bug #85621) was to be able to stop animations from eg. banner
servers (permanently) but keep animation in images from the site itself. So
making the stop button do it is not enough.

Comment 15

[Mitchell Stoltz (not reading bugmail)]

Recommend wontfix, but I leave it to a future module owner to decide. We can't
have per-site prefs for everything. Have to keep the feature bloat under
control. This would be a good Mozdev project if someone wanted to write one.