Simon Fraser [no longer active] Reporter
	Description • 22 years ago

In 4.x, I can hit the stop button after the page has finished loading, and it
stop s GIF animations. This also worked in Mozilla at some point. We need to
hook this up in Chimera.

	Akkana Peck
	Comment 1 • 22 years ago

This got regressed by the libpr0n landing and still isn't fixed -- see
discussion in bug 70030 (on which this one depends).

	Dean Tessman
	Comment 2 • 22 years ago

Isn't this a straight dupe of 70030?

	Simon Fraser [no longer active] Reporter
	Comment 3 • 22 years ago

No. We'd have to do some wiring in Chimera to hook this up.

	Dean Tessman
	Comment 4 • 22 years ago

Apologies, I forgot to look at the component.

	Michael Gabriel
	Comment 5 • 22 years ago

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

	Michael Gabriel
	Comment 6 • 22 years ago

oops, diff component

	Luke Kendall
	Comment 7 • 22 years ago

For some pages, the lack of this feature is enough to make me
close mozilla and re-open the page in Netscape or Konqueror.
So, this is just a comment that it's a worthwhile thing to fix.

luke

	Kathleen :Brade
	Comment 8 • 21 years ago

-->pinkerton

	Ruurd Koons
	Comment 9 • 20 years ago

What is the status of this bug? Camino nowadays still cannot stop animated gifs
by using the stop button or esc key.
If I read well, the bug this bug depends on is verified fixed

	Stuart Morgan
	Comment 10 • 20 years ago

The status of the bug is that it's not fixed, and is targeted for Camino 1.1 at
this point.

Out of curiosity, what's the rationale for this being a bug? Besides other Moz
browsers doing it, why should the stop button stop animating gifs? Should it
also stop all plugins, and javascript animations or timers?

	David Munch
	Comment 11 • 20 years ago

It should also stop flash/Shockwave. Mozz and FF does this.

	David Munch
	Comment 12 • 20 years ago

[i]Out of curiosity, what's the rationale for this being a bug? Besides other Moz
browsers doing it, why should the stop button stop animating gifs? Should it
also stop all plugins, and javascript animations or timers?[i]

As smfr responded on IRC: "because some people find [b]visual animation[/b] on
the page very annoying - it's an accessibility issue for some with visual
disabilities"

	David Munch
	Comment 13 • 20 years ago

On second thought, it really should stop everything on the page. Scripts,
animations, flash, etc.

	L. H.
	Comment 14 • 20 years ago

It seems better to have a different button or menu to stop animation instead of
making the stop button mean two different things.

	Anton P.
	Comment 15 • 20 years ago

I agree with Comment #14. A different button is needed since the two functions
are clearly completely different. I might wish to continue loading a long page
but stop multimedia features from running in the meantime. Hence this "bug" is
*not* a bug.

	Alexey Chernyak
	Comment 16 • 20 years ago

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

	Dave Yost
	Comment 17 • 19 years ago

Also: right-click on an animated gif or a movie of any kind should enable a Stop
Animation menu item.  And if there is an audio or an animated background image
that doesn't have its own obviously-clickable area, then right clicking on the
background should offer a Stop Animation and Sound menu item.

	Dave Yost
	Comment 18 • 19 years ago

If you're going to overload the stop button like this, then there should be
three states for the stop button, each with its own icon:
  stop loading
  stop animations
  resume

Some way to stop animations is a good idea.  But the real problem it seems to me
is that Camino needs to relegate animations to a lower-priority thread.  And
it's not even clear whether gets the hint that if I hide a window or scroll away
from an animated gif, there should be no CPU time used for animation.

	froodian (Ian Leue) Assignee
	Comment 19 • 18 years ago

This seems like a perfect candidate for an alternate menu item.  In the same way that Cmd-shift-R is force reload, Cmd-shift-. could be "force stop," which would stop all animations and plugins.

	Stuart Morgan
	Comment 20 • 17 years ago

I really think we should WONTFIX this, and open a more generic bug for having a way to stop and start animation. Stop, like back, forward, and reload, is a navigation button and should remain that way. This would create invisible (or, almost worse, visible but confusing if we change the icons) state controlling the behavior of the stop button. And how would starting work again? Press the reload button once to start animations, but twice to actually reload the page?

Overloading stop would be a UI mess that would make it harder to use.

	John David Galt
	Comment 21 • 16 years ago

I believe this is a dup of bug 21623.

	Stuart Morgan
	Comment 22 • 16 years ago

Since this is a UI-level bug, it's not.

	Stuart Morgan
	Comment 23 • 16 years ago

I continue to believe that this is a terrible idea, and I still haven't heard any good argument for taking this particular approach to dealing with animated images that would outweigh the UI problems, so I'm WONTFIXing it. If people have other specific suggestions, please file them as new bugs.