Re: [csswg-drafts] OS cursor size units and property (#12048)

Fingerprinting is unfortunate, but this feels like an important accessibility feature. Maybe an alternative would be something like `@media (cursor-size: [small, normal, large, extra-large])`. Fingerprinting would be a smaller issue if there's only a small set of options, instead of an arbitrary numeric value.

Though... does the result of the calculation need to be exposed? If this uses something like a % instead of a special unit, then it could just serialize back to that same percentage. I'm not aware of a way for web content to read the current cursor.

Alternatively: Just spec that browser vendors should respect the OS's cursor scale and automatically scale any cursor images to match. I don't think that's observable, and it means websites just work without authors having to worry about this.

A little tangential, but being able to specify a size for the cursor would also be useful for images without an implicit size. For one example, the SVG format, but also the spec [allows](https://drafts.csswg.org/css-ui-4/#ref-for-typedef-image) for any `<image>` type to be a cursor source instead of `<url>`, which also means gradients can be used. None of these have an implicit size. (You could argue that SVG does.)

-- 
GitHub Notification of comment by AtkinsSJ
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12048#issuecomment-2778056116 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 4 April 2025 09:23:14 UTC