W3C home > Mailing lists > Public > www-style@w3.org > March 2015

Re: [css3-ui] file formats for the cursor property

From: Tantek Çelik <tantek@cs.stanford.edu>
Date: Mon, 16 Mar 2015 01:39:54 -0700
Message-ID: <CAEV2_Wa-3Yqw-_9Q_Wm=QrM1bNhQ7Fyjq7i8wQhPb6iBYYt_qw@mail.gmail.com>
To: Patrick Dark <www-style.at.w3.org@patrick.dark.name>
Cc: Florian Rivoal <florian@rivoal.net>, "www-style@w3.org" <www-style@w3.org>
On Sun, Mar 15, 2015 at 8:18 PM, Patrick Dark
<www-style.at.w3.org@patrick.dark.name> wrote:
> On 3/12/2015 12:39 PM, Florian
>> In addition to a predefined list of values, the cursor property allows
>> authors to provide the cursor as an external file, indicated by the url()
>> function.
>> Unfortunately, the spec makes no mention of which file format must or
>> should be supported. It would be nice for authors to be able to depend on
>> something, and for test writing, having no format mandated makes things
>> tricky.
> I don't think it's a good idea to mandate image formats for the cursor
> property (at least not for level 3); it should be fine for implementors to
> effect only the cursor property's keywords. Otherwise, you're saying that
> anyone that wants to implement only the keywords isn't spec-compliant.

This is exactly why we have left cursor file formats unspecified and
not required. The situation has not changed since we discussed it
years ago.

Multiple implementations implementing a cursor file format is
*insufficient* to making such a format a must (or even a should).

For any such format we'd like to suggest, even as a should, we need
* an open spec we can normatively reference.

We don't have that, and we should not make CSS3-UI exiting CR dependent on that.

We can still use them for tests to show *a* way that implementations
interop, and thus show that the feature is *possible* to interoperably
implement, without making implementations non-compliant because of
choice of specific file format.

As far as what authors can depend on in terms of external formats,
that's more tutorial material than spec material.

This not a new issue (in general), HTML5 has (had?) the same issue
with <video> and <audio>.

We can start the process of asking for such specs (e.g. in a wishlist
for CSS4-UI), in the hopes that a future level of CSS-UI may be able
to normatively reference them.


Received on Monday, 16 March 2015 08:41:00 UTC

This archive was generated by hypermail 2.4.0 : Monday, 23 January 2023 02:14:49 UTC