-
-
Notifications
You must be signed in to change notification settings - Fork 265
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DFV: Clean up all selection limit enforcement #4197
Comments
A couple different ways we could handle Add New at first blush:
|
Handy package to test various relationship views. All the relationships are set to WordPress Pages, simply because that's where I already had a dozen or so test records. https://gist.github.com/pglewis/b15b71db343ecb19df8efae6c275b0a5 |
@sc0ttkclark: probably an executive decision on how to handle this one |
An idea -- disable add new button at selection limit but show some sort of text saying "you have reached the limit, remove items to select more"? |
That'll go hand in hand with the "Come up with a UI indicator that will explain why the UI isn't letting you select more items" task item. We'll need that even if they don't allow add new on the field. My thinking to this point is to have a message that the field is limited to N items and style that to red/alert whenever you're actually at the limit. |
@JoryHogeveen: any brainstorming / placement ideas in that direction? |
Or possible when AT the selection limit, when you disable the add-new button, add a message to the right of the button: You are at the selection limit. To add new records, remove an existing one first. |
Nicely done - agree with jim - it's alway better to be explicit if possible I would grey out the add new button too once the limit is reached |
Nice one @jimtrue. I'd say that should be fine! |
Messaging either next to add new button or above it in what Jim did an example of but not at top of list, it'd be at bottom of list. It might also be handy to see
Just an idea though. |
That was definitely the plan all along for that, no way we could leave the button normal without some visual indicator. Implemented now and ready to be tested. |
PR: #4218
[Edit: This has become a generic "sweep up selection limits" issue]
The text was updated successfully, but these errors were encountered: