[UX] Assets field with a limit of 1 shouldn't require explicit deselection when updating the selected asset

[piljac1]

Bug Description

Expected Behavior

When updating the current selection of an "Assets" field with a limit of 1, we should be able to select a new asset without having to explicitly deselect the currently selected asset (that should be automatically managed).

Current Behavior

When updating the current selection of an "Assets" field with a limit of 1, it requires the explicit deselection of the currently selected item before being able to select the newly desired asset.

I understand this behavior makes sense with a limit over 1, but it seems counterintuitive when the field is limited to a single asset.

How to Reproduce

Irrelevant to this issue, since it's pretty straight forward.

Environment

• Statamic 3.0.8 Pro (multi-site)
• Laravel 7.28.1
• PHP 7.4.3
• No addons installed

Install method: Fresh install from statamic/statamic

[github-actions[bot]]

This issue has not had recent activity and has been marked as stale — by me, a robot. Simply reply to keep it open and send me away. If you do nothing, I will close it in a week. I have no feelings, so whatever you do is fine by me.

[piljac1]

It wasn't implemented yet, so it is still a viable proposition.

[jasonvarga]

Agreed, but not a bug so I'll move to ideas.