Skip to content

Conversation

@JayGeorge
Copy link

This should close #12593, improving the UX when only 1/1 assets are selectable.

The asset browser already shows that only 1 asset is selectable on the bottom info bar, so I think that initial UX is fine…

2026-01-08 at 17 13 39@2x

But once you max-out the "Browse Assets" button now disappears

2026-01-08 at 17 20 22@2x

@duncanmcclean duncanmcclean linked an issue Jan 8, 2026 that may be closed by this pull request
…this helps. People may still want to browse assets, and the ability to drag and drop to upload remains anyway
@JayGeorge
Copy link
Author

JayGeorge commented Jan 9, 2026

I just updated this to a different approach.

On reflection, I don't think hiding the Browse Assets button helps. People may still want to browse assets, and the ability to drag and drop to upload remains anyway.
When observing clients using the Assets field, they tend to just drag images on there haphazardly anyway 😅

The most helpful thing is to show how many selections have been made vs the max. Glancing at this means you don't have to drag something onto the field or open the assets browser to check whether you can select another image.

This is a better approach compared to hiding controls that may still be useful.

2026-01-09 at 10 42 36@2x

I played with some other options before settling on this.

I tried…

  • Adding this info text below the field—but instructions can also go below, and it didn't feel as neat
  • Adding some colour as a warning, e.g. red when 5/5 or 1/1 are selected. However, quite often when browsing an entry, the assets are selected, and it's distracting to see a red pop-up when no action is needed.
  • Adding the info as a badge. I'm not totally against this, but it didn't feel quite as neat. This is more cursory information vs critical, so I went with inline bracketed text in the end.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[6.x] Assets fieldtype with max 1

2 participants