- From: Martin Raifer via GitHub <noreply@w3.org>
- Date: Tue, 21 Oct 2025 22:05:39 +0000
- To: public-css-archive@w3.org
tyrasd has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-ui] regression in definition of cursor values with URLs == #5831 introduced `url-set` definitions of the `cursor` property. However, it also introduced a subtle change in the https://github.com/w3c/csswg-drafts/commit/78fb03bd72db009decb0bdad200cd31f9dd9a235#diff-cc2f666bf7d93dcefcc3fffc4761793a54fba00c03b53b9dbdf81f5056f0b56eR604 before: ``` [ [<<url>> [ <x> <y> ]?,]* [ auto | … ] ] ``` after: ``` [ [ <<url>> | <<url-set>> ] [ <x> <y> ]? ]#? [ auto | … ] ``` While looking very similar, the two versions are not equivalent: the former requires a comma after each URL, resulting in a comma between the last URL and the "fallback" predefined cursor (e.g. as in `cursor: url(example.png), auto`). The latter does however use the `#`[^1] syntax which does not allow for a comma to be present after the list of URLs (e.g. hypothetically resulting in `cursor: url(example.png) auto`). [^1]: > A hash mark (#) indicates that the preceding type, word, or group occurs one or more times, separated by comma tokens As latter (`#?`) version is not backwards compatible to CSS Level 3, incompatible with how browsers currently handle the definitions of cursors using URLs and does not match the example given on the current draft version of the page as well as other related sources like [wpt](https://github.com/web-platform-tests/wpt/blob/master/css/css-ui/cursor-image-015-manual.html#L12), I assume this change was introduced by mistake. PS: with 1a57a4025c8778dab45ef8d5fbd482e4d6c4ebce, this mistake also made it into the CSS Level3 definitions on this repository. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13001 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 21 October 2025 22:05:40 UTC