That’s a shame. When the person wanting a feature is the one writing the code there is no problem understanding what the desired specifications are. When different, the specifications most often need to be “teased out” and all too often the goal post keeps moving.
Are you experienced with making mock-ups? They can go a long way in making it clear what end result is desired.
Even if you don’t know what programming might be needed, it would be best for you to make a list of details that is as complete as you can muster.
Because images are important to you, I’m assuming you’re more knowledgeable than I about what properties you want to preserve and which you’re willing to compromise. My take of “turn off cropping for tall images” is that you would like to have either a site-wide, or likely preferable per-post, setting. And that this setting would give the choice for the initial display (initial because they can be click-through to larger size better quality images) to either display in the container element preserving pixel quality at the expense of losing aspect ratio (cropped) or to preserve aspect ratio at the expense of losing pixel quality (resize).
Though not easy, I think the easier approach would be to have site-wide settings unless users lean towards being “techy”. In any case, I think there would need to be a list of “when this, then this” scenarios for programmers to work from. eg.
- when both the height and width are less or equal to the display area, display the original image
- when the height is <= display area but the width is greater crop or resize and letterbox
- same for when the width is <= but the height is greater
- when the image is both taller and wider than the display area … ?
- is the post-upload processing the same regardless of aspect ratio, any range of lengths, image type?
- when cropped, what area is to be used. top left, center?
- etc. etc.
The more detailed you can be about the specifications the more likely the code will be able to be worked up. Then it’s only a matter of a programmer being sufficiently motivated to write the code. eg. similar interest, financial compensation,