Context Navigation

Changes between Initial Version and Version 1 of Ticket #19393, comment 62

initial	v1
1	1	In the case where someone is using WordPress to create their own site or a site for a client in which they control, one can safely assume the correct crop position of an image. WordPress itself is making a default assumption that can be incorrect, too.
2	2
3		That said, a possible solution may be to allow theme developers to define a default crop that best fits the intended purpose and will more than likely be the correct assumption a majority of the time. Then, with an improved WP_Image_Editor, users can re-crop the image as desired. It might even be advantageous to create a "Quick Crop" option to select on of the various image crop positions (top left, top center, top right, etc.).
	3	That said, a possible solution may be to allow theme developers to define a default crop that best fits the intended purpose and will more than likely be the correct assumption a majority of the time. Then, with an improved WP_Image_Editor, users can re-crop the image as desired. It might even be advantageous to create a "Quick Crop" option to select one of the various image crop positions (top left, top center, top right, etc.).
4	4
5	5	Anything we can do to help the users experience will be a bonus, and being able to define a crop position where it makes sense is one of them. More often than not, a crop position will not need to be set. But again, when working on projects you control, this would be very helpful. Not allowing a default crop position to be set just seems silly.