W3C home > Mailing lists > Public > www-style@w3.org > November 2014

Re: [css3-ui] using <image> instead of <uri> in cursor (Issue 44)

From: Dirk Schulze <dschulze@adobe.com>
Date: Tue, 25 Nov 2014 17:55:34 +0000
To: Florian Rivoal <florian@rivoal.net>
CC: www-style list <www-style@w3.org>, Tantek Çelik <tantek@cs.stanford.edu>, "rbyers@chromium.org" <rbyers@chromium.org>
Message-ID: <BA899901-247C-492D-B7C5-8EC5EC7D692C@adobe.com>

On Nov 25, 2014, at 2:10 PM, Florian Rivoal <florian@rivoal.net> wrote:

> Raised in issue 44: https://wiki.csswg.org/spec/css3-ui#issue44
> currently, the cursor property takes its images from a list of <uri>. It should use a list of <image> instead, to get access to the various functional notations defined for this value type. This is backward compatible as <uri> is a valid value of <image>.

I agree for CSS UI level 4. As you said, <image> is backward compatible. However, I am not so sure if linear/radial gradients and all other <image> values are supported in all browsers. My suggestion is to change it in the next level.


> Among other things (gradients, image fragments, crossfade...), this gives access to image-set(), which is needed to have high resolution cursor on “retina” displays.
> Proposed patch attached.
> - Florian
> <image-cursor.patch>
Received on Tuesday, 25 November 2014 17:56:08 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:51:49 UTC