Nice work! However there are quite a few components with clickable parts that include text. These include:

• FAB / extended FAB
• Chips
• Tabs
• Navigation (rail, drawer, bar)
• Top app bar
• XListTiles (e.g. CheckboxListTile)
• Menus
• Date and time pickers

Rather than handle these individually, can we add it a level below, say to InkWell and see which components still need to be handled individually?

Rather than handle these individually, can we add it a level below, say to InkWell and see which components still need to be handled individually?

I agree with this. Let me try to update this PR.
First goal of this PR was to get feedback for the DefaultSelectionStyle.mouseCursor solution I proposed. I choosed Material buttons to illustrate how this can be used but it makes sense to use it for InkWell to reduce code duplication.

Thanks for fix. On which channel and which version this fix is available?

This fix is available on the master channel.

pro tip: d4f884e indicates the branches the merge commit is present on

Thanks for the fix. Is it also available in stable or only on master?

As long as stable isn't listed on that commit, it's not available. Since beta releases are monthly, expect it in the next one.

@guidezpl still not available on stable?

@LucaIaconelli I see that is present in stable from version 3.13.0

https://docs.flutter.dev/release/release-notes/release-notes-3.13.0

For future reference (both for myself and others), here's an example of how this output can be utilized effectively:

SelectionArea(
  child: DefaultSelectionStyle.merge(
    mouseCursor: SystemMouseCursors.click,
    child: Text('Clickable and selectable text'),
  ),
);