Closed Bug 4417 Opened 26 years ago Closed 26 years ago

Animated GIFs flicker upon drawing new frame

Categories

(Core :: Graphics: ImageLib, defect, P3)

defect

Tracking

()

VERIFIED WORKSFORME

People

(Reporter: elig, Assigned: pnunn)

Details

* TITLE/SUMMARY
Animated GIFs flicker upon drawing new frame

* STEPS TO REPRODUCE
0) Launch Apprunner
1) View an animated GIF. (e.g. banner ads at top of almost all of the Netscape
web site; for a more radical example, try www.animation.com)

* RESULT
 - What happened

Image flickers in between frames, rather than cleanly redrawing the new frame
onto the most recently drawn frame.

The "flicker" looks like Gecko is momentarily showing the page background behind
the frame in between drawing frames.

Most noticable on Mac OS & Linux. (less noticable on Win32)

 - What was expected

Behavior equivalent to Communicator/IE 4.

* REGRESSION

 - Occurs On
        Mac OS Apprunner (3.29.99 optimized build)
        Win32 Apprunner (3.29.99 optimized build [NT 4, Service Pack 3])
        Linux Apprunner (3.29.99 optimized build)

 - Doesn't Occur On
        Mac OS Communicator 4.5 (RTM)


* CONFIGURATIONS TESTED

- [Mac] Power Mac 8500/120 (233 Mhz 604e), 64 MB RAM (VM on; 1 MB of VM used),
1024x768 (Thousands of Colors), Mac OS 8.5.1

- [Win32] Vectra VL (233 Mhz P2), 96 MB RAM, 800x600 (True Color), NT 4.0 SP3.

- [Linux] Vectra VL (266 Mhz P2), 96 MB RAM.
Target Milestone: M6
Status: NEW → ASSIGNED
Does this condition still exist?
-pn
Hmm...this has been sporadic, and has no longer been a problem in most recent
builds.

Using today's AM builds (4.20.99) on Linux/Mac OS/Win32, I'm not seeing any
problems.

So, you may wish to mark this as 'worksforme', and I'll re-open it if it recurs.

Thanks!
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
okey doke.
-pn
Status: RESOLVED → VERIFIED
Using the 4.27.99 builds, I still don't see this problem on any platform in
animated GIFs.

Thus, Verified WORKSFORME, and will re-open if the problem recurs.
You need to log in before you can comment on or make changes to this bug.