Image minimum and maximum resolutions should be configurable per field instance (for fields of Reference type Media with Media type Image) and these should be honored when uploading new images or selecting existing ones from the media library

Updated issue summary. I dropped the part about configuring maximum resolutions per field because i don't see the use case; if it is a server space limitation that would be sitewide, no?

@mlncn being able to configure the maximum resolution is absolutely critical to the problem we were experiencing, where people were uploading images that were way too big for Drupal to process (3840 pixels in either dimension seems to be the breakpoint). The uploads would appear to finish, but none of the image styles could be processed from it.

Patch #24 solved that problem for us, allowing people to upload images of any size via any field which would then be properly resized and processed.

Thanks, Kasey. Setting max resolution is critical for us as well. It's about making the images fit for purpose. We want to prevent users from bogging down the site storage with 5000px wide images that will only ever be used as a 100px wide thumbnail.

Does the patch also take care of the #2nd(when selecting existing images from the media library) use case mentioned in the issue description?

@rajeevgole: no I don't believe it does. It seems to alter only the Media library upload form.

I'm not sure the patches in #24/26 address the original issue. I think they are (and I am) looking for a way to control the image resolution from a Media reference field, with Image media as an allowed type, rather than from the Image field within a Media type. I realize this means two places where min/max can be configured, but I'm really trying to avoid creating a separate Media type for images where I want to control the resolution at time of upload.

It's possible that this just isn't how Media entities are intended to be used in Drupal 8/9/10+, but if that's the case, I'm struggling to find any documentation to that effect or a good workaround for my use case. The entity_browser → module provides the "Upload images as media items" widget that allows you to specify an upload location, which overrides the selected Media type's location, so maybe that's a more appropriate place for this kind of feature.

Rerolled patch from #26 against 11.x branch.

Have not tested

But issue summary should be updated to match standard template please

Sounds like something that could use some test coverage also.

Thanks.