The Tor Browser / file revision

 # GIF tests 

 # tests for bug 519589

 == 1bit-255-trans.gif 1bit-255-trans.png

 == in-colormap-trans.gif in-colormap-trans.png

 == out-of-colormap-trans.gif out-of-colormap-trans.png

 # a GIF file that uses the comment extension

 == comment.gif comment.png

 # a GIF file with a background smaller than the size of the canvas

 == small-background-size.gif small-background-size-ref.gif

 == small-background-size-2.gif small-background-size-2-ref.gif

 # a transparent gif that disposes previous frames with clear; we must properly

 # clear each frame to pass.

 random == delaytest.html?transparent-animation.gif transparent-animation-finalframe.gif # incorrect timing dependence (bug 558678)

 # test for bug 641198

 skip-if(B2G) random-if(Android) == test_bug641198.html animation2a-finalframe.gif # bug 773482

 # webcam-simulacrum.mgif is a hand-edited file containing red.gif and blue.gif,

 # concatenated together with the relevant headers for

 # multipart/x-mixed-replace. Specifically, with the headers in

 # webcam-simulacrum.mjpg^headers^, the web browser will get the following:

 #

 # HTTP 200 OK

 # Content-Type: multipart/x-mixed-replace;boundary=BOUNDARYOMG

 # 

 # --BOUNDARYOMG\r\n

 # Content-Type: image/gif\r\n

 # \r\n

 # <contents of red.gif> (no newline)

 # --BOUNDARYOMG\r\n

 # Content-Type: image/gif\r\n

 # \r\n

 # <contents of blue.gif> (no newline)

 # --BOUNDARYOMG--\r\n

 # 

 # (The boundary is arbitrary, and just has to be defined as something that

 # won't be in the text of the contents themselves. --$(boundary)\r\n means

 # "Here is the beginning of a boundary," and --$(boundary)-- means "All done

 # sending you parts.")

 skip-if(B2G) HTTP == webcam.html blue.gif # bug 773482