[css3-ui] cursor image format tests

Hello Public-css-testsuite,

Spurred on by recent discussions around mandated image formats for the
CSS cursor property, I have submitted some tests.

http://test.csswg.org/shepherd/search/testcase/spec/css-ui-3/section/6.1.1/load/t53/#t16

A) cursor-image-001.html to cursor-image-009.html are basic tests just to
have a quick look at image format support for cursors:

001   PNG image with css-supplied hotspot, relative URL.
002   PNG image with css-supplied hotspot, absolute URL.
003   ICO cursor with its own hotspot, relative URL.
004   CUR cursor with its own hotspot, relative URL.
005   SVG cursor with CSS-supplied hotspot, relative URL.
006   ANI cursor with its own hotspot, relative URL.
007   Compressed (SVGZ) cursor with CSS-supplied hotspot, relative URL.
008   Non-existent image with CSS-supplied hotspot, relative URL, and help cursor fallback
009   PNG image with css-supplied hotspot, relative URL, no fallback.

B) One test is exploratory, an SVG cursor where the SVG has a viewBox but
no hardcoded width and height. CSS3-UI does not say what to expect in
this case. Unlike most other places where images are used in CSS,
there is no way to say in the CSS what size is wanted.

cursor-image-005-nfs.html

C) A larger set of tests extensively checks PNG cursor support in
depth (no need to run these if 001 and 002 fail). All possible color
types (greyscale, RGB, grey+A, RGBA, indexed) are tested with both
interlaced and non-interlaced images, at various bit depths.

PNG alpha and transparency (tRNS) are tested, also gamma correction.
Lastly there are some tests with invalid PNG images, to check the
fallback is used.

All images are from the PNG test suite, and the images were verified
for correctness to the PNG spec using pngcheck -v.

cursor-image-png-001.html to cursor-image-png-043.html

D) Similar tests will be needed for other cursor formats, some of which
(such as .cur) do not have adequate documentation.

E) I have not yet written tests for hotspot position (apart from
merely parsing the values in the CSS), but plan to.

It would be great to have these reviewed so that we can start testing
browsers against them. I have found a number of firefox bugs, for
example, and will log them in the Firefox bugzilla.



-- 
Best regards,
 Chris Lilley, Technical Director, W3C Interaction Domain

Received on Monday, 23 March 2015 16:01:31 UTC