Closed Bug 269843 Opened 20 years ago Closed 19 years ago

gif animation restarts after being stopped if image is present in other tab

Categories

(Core :: Graphics: ImageLib, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 332973

People

(Reporter: bugzilla, Assigned: pavlov)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

A stopped gif animation will continue if a link to a page containing the same
gif is opened.

Gif animations can be stopped by pressing escape. When another page references
to the same URL, the gif animation continues on the page where it has been stopped.

Reproducible: Always
Steps to Reproduce:
1. Go to http://stock.ter.dk/anim_1.php or create a couple of pages with the
same gif animation
2. Press escape to stop the animation
3. Open a new tab where the gif animation is present

Actual Results:  
The gif animation continues on the page where it has been stopped

Expected Results:  
The gif animation should still have been stopped.

The problem is present in Mozilla 1.7 as well, and Firefox 1.0 under Linux.

It might be related to the behaviour mentioned in bug #129986
If it's the same image, imagelib will only allow us to animate it in all windows
or not animate it in all windows....  It only has a single object for the image.
*** Bug 287582 has been marked as a duplicate of this bug. ***
> If it's the same image, imagelib will only allow us to animate it
> in all windows or not animate it in all windows....  It only has 
> a single object for the image.

Then it sound like imagelib needs to be able to represent
different occurrences that are of the same images but that
have different states (e.g., moving vs. stopped).
OS: Windows XP → All
Hardware: PC → All
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
This bug still exists in Mozilla 1.7.12 (Mozilla/5.0 (Windows; U; Windows NT 5.1; 
en-US; rv:1.7.12) Gecko/20050915).
This bug still exists in Mozilla 1.7.12 (Mozilla/5.0 (Windows; U; Windows NT 5.1; 
en-US; rv:1.7.12) Gecko/20050915).

Hey, why can't I changed this one back to UNCONFIRMED?
Duping forward to bug 332973, which is the open bug that covers the underlying issue here.  (see in particular bug 332973 comment 9)
Resolution: EXPIRED → DUPLICATE
You need to log in before you can comment on or make changes to this bug.