Closed
Bug 152054
Opened 23 years ago
Closed 23 years ago
Wrong animated GIF processing
Categories
(Core :: Graphics: ImageLib, defect)
Tracking
()
People
(Reporter: vladimir, Assigned: pavlov)
References
()
Details
Actually the processing of animated GIF is not the same as in IExplorer.
Example on the page http://www.strannik.de/akme/body/index.htm.
In IE it is a flying horse. In Mozilla it is a wrong picture
Comment 1•23 years ago
|
||
Reassigning.
Assignee: morse → pavlov
Component: Image Blocking → ImageLib
QA Contact: tever → tpreston
Comment 2•23 years ago
|
||
Looks like a flying horse to me.. Win2k Build 2002061204
Reporter, when creating bug reports, please include the Build ID in which you
have saw the bug.
Comment 3•23 years ago
|
||
wfm with win2k build 20020613..
Comment 4•23 years ago
|
||
wfm 20020613 - linux
Reporter | ||
Comment 5•23 years ago
|
||
I repeat what is the problem.
The gif-file
http://www.strannik.de/akme/bodyfly.gif on the page
http://www.strannik.de/akme/body/index.htm is shown correct by Internet Explorer
as a fkying horse, and NOT CORRECT in Mozilla.
What I really see, it is like in the file
http://www.strannik.de/akme/wronghorse.jpg
It is wrong processing of animated gif, when the horse does not fly, but prolong
itself
Build ID=2002053012, I have started Mozilla yesterday
Comment 6•23 years ago
|
||
wfm also on ppc linux 20020607
Maybe you have broken data in cache?
Try to hit SHIFT+Reload-Button, this will force mozilla to reload the
pagecontent from the internet, not from cache..
does that solve your problem?
Comment 7•23 years ago
|
||
I find the same problem with http://www.negocios.pt/Imagens/Fixo/registo.gif
Win XP - buid 2002061104
Luis Freire
Comment 8•23 years ago
|
||
Resolving to bug that fixed this, based on Comment #5. Download a nightly or
wait for 1.1b to come out. Or read the dup'd to bug to see that status of the
1.0.x checkin.
*** This bug has been marked as a duplicate of 85595 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•