830211 - Two instances of an <img> (in different documents) share the same animation timing

Status: RESOLVED DUPLICATE of bug 332973

(Core :: Graphics: ImageLib, defect)

Description

[Philip Rogers]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_7_5) AppleWebKit/537.22 (KHTML, like Gecko) Chrome/25.0.1364.29 Safari/537.22

Steps to reproduce:

1) Open two windows and position them so both are visible.
2) In the first window, navigate to http://philbit.com/animatebug.html
3) Let the animation play for a bit.
4) In the second window, navigate to http://philbit.com/animatebug.html


Actual results:

The animation in the second windows does not start at t=0 but instead uses the timing from the first windows and starts halfway through the animation.


Expected results:

For each new document, SVG SMIL timing should start at t=0.

Comment 1

[Daniel Holbert [:dholbert]]

(In reply to Philip Rogers from comment #0)
> For each new document, SVG SMIL timing should start at t=0.

That statement is orthogonal to what your STR demonstrate.

For each new document, SVG SMIL timing *does* start at t=0. (To demonstrate this, try loading your SVG file ( http://philbit.com/mouse.svg ) directly, in two separate tabs.  You'll see that each does, indeed, get its own SMIL timeline.)

Now -- your STR exercise something different than that. They've got instances of the *same* image, which happen to be hosted in different documents.  Since we use a global image cache, those images map to a single (behind-the-scenes) document -- so yes, they end up sharing a timeline.

I believe there's a very old bug about "don't share animated image timelines between different tabs" (though IIRC, the imagelib module owner/peers haven't yet stated that that's a bug we want to fix).

This is probably a dupe of that old bug.

Comment 2

[Daniel Holbert [:dholbert]]

(In reply to Daniel Holbert [:dholbert] from comment #1)
> Now -- your STR exercise something different than that. They've got
> instances of the *same* image,[...]
> Since we use a global image cache[...] they end up sharing a timeline.

Meant to say -- there's nothing SVG-specific about that ^^ -- it's true of all animated image formats in Gecko.