- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Sep 2017 07:15:14 +0000
- To: public-css-archive@w3.org
> What currently happens in browsers? Do they use the SVG, but scale it to 0px square? Or do they ignore it like a broken image, and fall back to default system cursors? The later. Well, they fallback, but not directly to system cursors, they fallback to the chain you've defined. If you have `cursor: non-fixed.svg, fixed.svg, foo.ico, resize`, browsers that support svg in cursors (all but Edge) will fallback to fixed.svg, Edge will fallback to foo.ico, and a theoretical browser that supported none of this would fallback to `resize`. > I would prefer a platform-specific default size, rather than ignoring it altogether. That is what the spec currently calls for: > 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. where `default object size` is a term that redirects to the css-image spec, which results in what you'd want: display non-intrinsically sized images at the largest size that fits within `default object size` without distorting its aspect ratio if it has one. > A 300px by 150px cursor is probably not a good default. Indeed:) 16x16 is likely a better starting point (in device independent CSS pixels, so 32x32 on a retina screen, and so on), keeping in mind that this isn't the largest size, but the default size. -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1813#issuecomment-329701978 using your GitHub account
Received on Friday, 15 September 2017 07:15:08 UTC