tor-browser

The Tor Browser
git clone https://git.dasho.dev/tor-browser.git
Log | Files | Refs | README | LICENSE

reftest.list (2996B)


      1 # JPEG tests
      2 
      3 # Images of various sizes.
      4 == jpg-size-1x1.jpg   jpg-size-1x1.png
      5 == jpg-size-2x2.jpg   jpg-size-2x2.png
      6 == jpg-size-3x3.jpg   jpg-size-3x3.png
      7 == jpg-size-4x4.jpg   jpg-size-4x4.png
      8 == jpg-size-5x5.jpg   jpg-size-5x5.png
      9 == jpg-size-6x6.jpg   jpg-size-6x6.png
     10 == jpg-size-7x7.jpg   jpg-size-7x7.png
     11 == jpg-size-8x8.jpg   jpg-size-8x8.png
     12 == jpg-size-9x9.jpg   jpg-size-9x9.png
     13 == jpg-size-15x15.jpg jpg-size-15x15.png
     14 == jpg-size-16x16.jpg jpg-size-16x16.png
     15 == jpg-size-17x17.jpg jpg-size-17x17.png
     16 == jpg-size-31x31.jpg jpg-size-31x31.png
     17 == jpg-size-32x32.jpg jpg-size-32x32.png
     18 == jpg-size-33x33.jpg jpg-size-33x33.png
     19 # Progressive encoding
     20 == jpg-progressive.jpg jpg-progressive.png
     21 # Grayscale colorspace
     22 == jpg-gray.jpg jpg-gray.png
     23 # CMYK colorspace
     24 == jpg-cmyk-1.jpg jpg-cmyk-1.png
     25 == jpg-cmyk-2.jpg jpg-cmyk-2.png
     26 # This intermittently fails on Android due to async image decoding (bug #685516)
     27 # Sometimes the image decodes in time and the test passes, other times the image
     28 # appears blank and the test fails. This only seems to be triggered since the
     29 # switch to 24-bit colour (bug #803299).
     30 random-if(Android) == jpg-srgb-icc.jpg jpg-srgb-icc.png
     31 
     32 # webcam-simulacrum.mjpg is a hand-edited file containing red.jpg and blue.jpg,
     33 # concatenated together with the relevant headers for
     34 # multipart/x-mixed-replace. Specifically, with the headers in
     35 # webcam-simulacrum.mjpg^headers^, the web browser will get the following:
     36 #
     37 # HTTP 200 OK
     38 # Content-Type: multipart/x-mixed-replace;boundary=BOUNDARYOMG
     39 #
     40 # --BOUNDARYOMG\r\n
     41 # Content-Type: image/jpeg\r\n
     42 # \r\n
     43 # <contents of red.jpg> (no newline)
     44 # --BOUNDARYOMG\r\n
     45 # Content-Type: image/jpeg\r\n
     46 # \r\n
     47 # <contents of blue.jpg> (no newline)
     48 # --BOUNDARYOMG--\r\n
     49 #
     50 # (The boundary is arbitrary, and just has to be defined as something that
     51 # won't be in the text of the contents themselves. --$(boundary)\r\n means
     52 # "Here is the beginning of a boundary," and --$(boundary)-- means "All done
     53 # sending you parts.")
     54 HTTP == webcam-simulacrum.mjpg blue.jpg
     55 # Same as the above but as img elements in html files to get better test
     56 # coverage of multipart images.
     57 # Images loaded at the top level are actually loaded into an ImageDocument
     58 # which is a slim html document wrapper around the image.
     59 # Multipart images send multiple OnStartRequest's, each OnStartRequest causes
     60 # us to create a new ImageDocument to show the next part.
     61 # This differs from displaying a multipart image in an img element in a regular
     62 # document where we use the same document and same elements and same layout
     63 # frames for each part. So we have this testcase to test those different
     64 # codepaths.
     65 HTTP == webcam-simulacrum.html blue.html
     66 
     67 == non-interleaved_progressive-1.jpg non-interleaved_progressive-1-halfred-ref.png
     68 == non-interleaved_progressive-2.jpg non-interleaved_progressive-2-white-ref.png
     69 
     70 == red-bad-marker.jpg red.jpg
     71 
     72 # check that we reject jpegs with > 1000 scans
     73 == jpg-progressive-1000.html jpg-progressive-1000-ref.html