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

On Tue, Nov 25, 2014 at 12:55 PM, Dirk Schulze <dschulze@adobe.com> wrote:

>
> 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.
>

Right.  Blink (and I believe still WebKit) currently support only
<https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/core/css/parser/CSSPropertyParser.cpp&q=file:WebKit%20file:parser%20cursor&sq=package:chromium&type=cs&l=628>
image-set.


>
> Greetings,
> Dirk
>
> >
> > 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>
>
>