This is more like a workaround for now. Background details:
On our system, for a so far unknown reason, the exif data (does not depend on the test image, the exif data is as usuall but its not correctly respected somehow) is somehow in cases of 6 and 8 (see exif orientation screenshots in article of next url) not correctly processed with the core "auto_orient" checkbox option (images are NOT rotated correctly)
This commit intoduces a seperate, additional handling, which basically "inverts" the image-orientation in exif data cases 6 and 8.
....so thats why i introduced in this branch the additional option. Of course, in best case it would not be needed at all but so far at least it provides a workaround for us and maybe its helpfull for others ... :-)
This is more like a workaround for now. Background details:
Overall: It seems somehow not always reliable how to act on the EXIF data. In theory i would totally agree and say that the approach described and explained here (https://jdhao.github.io/2019/07/31/image_rotation_exif_info/) and also currently taken in the core of the extension should be correct, but, under some (sadly not yet absolutely clear) circumstances, the auto-orient feature does not work - at least on our new server. And i could imagine that the same happens for the user (https://github.com/DTM-TYPO3)´s usecase in this issue https://github.com/xperseguers/t3ext-image_autoresize/issues/60
Also, the problem has been reported and studied already by others like:
....so thats why i introduced in this branch the additional option. Of course, in best case it would not be needed at all but so far at least it provides a workaround for us and maybe its helpfull for others ... :-)