require-baseline: Property 'cursor' is not a widely available baseline feature

[nzakas]

It appears that the cursor property is not considered baseline even though it has been around for a while:
https://github.com/web-platform-dx/web-features/blob/main/features/cursor.yml#L9

Options

We have a couple of ways of addressing this:

1. We could manually override the settings for cursor. We'd then need to make this determination on a case-by-case basis for any other similar properties.
2. We could add an option to the rule that lets people specifically allow specific properties. This would put the responsibility on users to decide how strictly they want to follow baseline.

Discussed in #50

^{Originally posted by sysmat February 17, 2025}
From where is this rule, and why?

[nzakas]

Ping @eslint/eslint-tsc

[mdjermanovic]

I'm fine with implementing both solutions at the same time. We could override the data ourselves when it seems incorrect and also add an option to let users specify properties they'd like to allow regardless of our data.

[fasttime]

It seems that cursor is not supported in Safari for iOS, and that explains why it's not included in the baseline. This isn't really surprising because iOS is designed to run on mobile devices that are used without a mouse and have little need for a mouse pointer. It's possible that Safari for iOS intentionally decided not to adopt the cursor standard for usability purposes, in which case that feature won't be added to the baseline anytime soon.

I think it's fine to override the baseline defaults in this case. Providing an additional option to selectively override certain baseline features could be also useful.

[nzakas]

It looks like they're aware of the problem and are working towards a solution:
web-platform-dx/web-features#1038

In the near-term, I'll just manually update cursor. We can leave this open to determine if we need to add a new option to the rule as well.