Epic #77810: Improve (responsive) image handling
Image Manipulation on Portrait images - wrong display in frontend?
I recognized a strange behaviour on image content elements + image manipulation with portrait images (landscape works like a charm)
I have an image content element with 3 images per row, all of them cropped with 1:1 ratio. (see Image_Manipulation_BE_1.png / Image_Manipulation_BE_2.png / Image_Manipulation_BE_3.png)
In Frontend all images are rendered in different ratio / height, see Image_Manipulation_FE.png
Testet on TYPO3 7.6.1
#1 Updated by Frans Saris almost 4 years ago
- Status changed from New to Needs Feedback
What do you use to render the frontend? CSS_styled_content, fluid_styled_content or something custom? What are the settings for alignment, columns etc of the content element? Try setting it to 1 column aligned top center to see if fe ratio is then correct.
#4 Updated by Jan Perdoch over 3 years ago
Yes, in the backend the cropping is wrong after save. In crop editor still shows correctly cropped area. But - when I open image in desktop editor and use values from crop editor (x,y,w and h), it's same wrong cropped image, as after Save in backend. I CAN'T crop it as I want in editor.
But, when I'm trying different portrait image - on the same page, in the same content element, behavior it's completely different. I created matrix 200x300 with 50px squares. I'm attaching screenshot of result: crop (100x100 from point [50,50]), save and open again. Cropped image is correct, but in editor is wrong area and start point. I CAN crop it as I want, in this case.
I took the third test, and it seems to be same as in the second. Correctly cropped, but wrong in editor in the next editation.
#6 Updated by David Rellstab over 3 years ago
Same Problem here (Version 7.6.6, CSS_styled_content). Thumbnail correctly displayed after cropping, but after saving the crop is shifted (sometetimes more, sometimes less, depending on the crop position you intened). If I don't move the initial crop position (center) it works as expected.
#11 Updated by Rafal Brzeski over 2 years ago
- File Zrzut ekranu 2017-01-04 o 11.53.58.png View added
- File Zrzut ekranu 2017-01-04 o 11.41.20.png View added
- File Zrzut ekranu 2017-01-04 o 11.43.24.jpg View added
- File Zrzut ekranu 2017-01-04 o 11.53.43.png View added
I found where the problem is.
Crop editor (Image manipulation) use dimension of image from Camera data, not real physical dimension!
See my explanation on screenshots.
#13 Updated by Rafal Brzeski over 2 years ago
- File Test.zip added
Good point Frans, in my case i use extractor -> https://typo3.org/extensions/repository/view/extractor
and this extension maps Exif dimension data to fields which corresponds to image manipulation.
So i guess that my case should be report to author (Xavier Perseguers) of extractor, right ?
In any case I have attached my "Test.jpg" image in zip.
#14 Updated by Xavier Perseguers over 2 years ago
Extractor takes the info from EXIF, right, but if they differ from the physical size, then it may be related to 2 different use cases:
- Image was resized (e.g. in Photoshop) prior to upload and metadata is from the original file, not the uploaded one
- Image was resized upon upload (e.g., EXT:image_autoresize)
If this happens, it looks like the crop editor should trust the metadata, when it exists since an extractor who populated the info (this is a read-only info thus cannot be changed by an editor) may be in a position to know "more" about the image than just by reading the EXIF data.
If the FAL metadata are not populated, then it's fine to read the EXIF of course, but only as failover.
Did not investigate more, if EXT:extractor may be enhanced in some way, do not hesitate to suggest change.
#16 Updated by Alexander Opitz about 2 years ago
- Status changed from Needs Feedback to Closed
No feedback within the last 90 days => closing this issue.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.