- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Wed, 20 Sep 2017 17:58:07 +0000
- To: public-css-archive@w3.org
OK, working on actual spec text. The [current text in CSS UI 3](https://drafts.csswg.org/css-ui-3/#cursor): > The UA must support the following image file formats: > > - PNG, as defined in [PNG] > - SVG, as defined in [SVG11], in secure static mode [SVG2] > - any other non-animated image file format that they support for `<image>` in other properties, such as the the background-image property > > In addition, the UA should support the following image file formats: > > - SVG, as defined in [SVG11], in secure animated mode [SVG2] > - any other animated image file format that they support for `<image>` in other properties, such as the the background-image property > > The UA may also support additional file formats. > > ... > > The default object size for cursor images is a UA-defined size that should be based on the size of a typical cursor on the UA’s operating system. As I'm reading the IRC notes (sorry I missed the call), the changes should be: - Add a qualification to both "The UA must support the following image file formats" and "the UA should support the following image file formats", saying "for images with [intrinsic dimensions](https://drafts.csswg.org/css-images-3/#intrinsic-dimensions)". (Added at the top of the list, not in the SVG bullet point, so that it includes both SVG and the "any other format" item). - After "The UA may also support additional file formats" add something like "In particular, the UA may support images without intrinsic dimensions, by using a UA-defined default object size for cursor images, which should be based on the size of a typical cursor on the UA’s operating system." - (Then remove the extra paragraph that has been moved up into the "may" section.) - Maybe (?) add an informative note explaining that the CSS WG would really like to add normative support for cursors without intrinsic dimensions, if only UAs would be so kind as to implement it. I personally would have argued for adding no-intrinsic size to the "should" list, instead of "may" but... anyway. Not a big difference in practice. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1813#issuecomment-330931371 using your GitHub account
Received on Wednesday, 20 September 2017 17:57:59 UTC