I guess the relevant bit of spec text here is this:

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

Don't know if we have any good platform-specific values like that. Maybe f* kMaximumCursorSize (128) is something we can use (f=0.5 or so?)

Are all the built-in cursors (all) delegated to the OS, or are there images bundled with the browser itself? If you're using images, use the same size?

Otherwise, (assuming these sizes are in css pixels, not device pixels), I think f = 0.25 to f = 0.5 seems like a reasonable range. Or maybe skip making it dependent on the maximum size, and shoot straight for 32px to 64px.

The built-in cursors are mapped to OS cursors by the platform layer, so I don't think any size is readily available there. For image cursors the intrinsic size is (always) used (which means we get 0x0 in this case.)
Yes, if we randomly pick a dimension to use for the default object size, it needn't depend on the max size (and it may even be tricky to do in a nice way due to impl. layering.)

This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot