Description

This PR adds default cursor and/or mouseCursor property to a number of widgets.

This PR also adds MaterialStateMouseCursor, which is a mouse cursor that depends on material states, as well as ClickableMouseCursor, which is a material state mouse cursor that is click normally but basic when disabled.

The complete list of widgets are as follows:

• InkWell
• InkResponse
• RawMaterialButton
• MaterialButton
• IconButton
• FloatingActionButton
• RaisedButton
• OutlineButton
• FlatButton
• ToggleButtons
• Switch
• Radio
• Checkbox
• PopupMenuItem
• Tabs
• ModalBarrier (no property, only default cursor basic)
• EditableText (no property, only default cursor text)
• SelectableText (no property, only default cursor text)
• TextField
• Slider
• BottomNavigationBar
• ListTile
• FocusableActionDetector

Open question

• Is there a better name for ClickableMouseCursor?
• Should we implement MaterialStateMouseCursor in a currying-like way so that the states of InkResponse can be directly used?

Related Issues

• Part of Add the ability to programmatically change mouse cursors. #31952

Tests

I added the following tests:

• For every widget, the following tests are added:
  • Every constructor correctly applies mouseCursor property
  • The default mouse cursor is correct
  • If the default mouse cursor is ClickableMouseCursor, then the widget displays the correct cursor when disabled.

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I signed the CLA.
• I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I updated/added relevant documentation (doc comments with ///).
• All existing and new tests are passing.
• The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Did any tests fail when you ran them? Please read Handling breaking changes.

• No, no existing tests failed, so this is not a breaking change.
• Yes, this is a breaking change. If not, delete the remainder of this section.
  • I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
  • I got input from the developer relations team, specifically from: Replace with the names of who gave advice
  • I wrote a migration guide: Replace with a link to your migration guide