Created attachment 382050 [details] Reproducible Image Input Currently, Native media resizing feature drops orientation exif value, nor rotate image as per its orientation value. If input image has non-portrait orientation exif value, resize output image will be shown as invalid orientation. Please refer to Github Issue of native-media-resizing repository for details: https://github.com/addyosmani/native-media-resizing/issues/1#issuecomment-545980413 Tested in iPhone X, iOS 13.1.3 Safari, and attached reproducible input image.
<rdar://problem/56689947>
What do you mean by "native media resizing"? Is this a JS library that does image resizing?
Created attachment 382224 [details] System UI Prompt 1
Created attachment 382225 [details] System UI Prompt 2
Created attachment 382226 [details] System UI Prompt 3
(In reply to Simon Fraser (smfr) from comment #2) > What do you mean by "native media resizing"? Is this a JS library that does > image resizing? No, It's a system feature. I mean, Starting from iOS 13, User can change quality of selected image before file uploading. For example, When HTML page has <input type="file"> element and when user clicks it. A system prompt (https://bugs.webkit.org/attachment.cgi?id=382224) will be shown. and Photo Library will be opened when user clicks "Photo Library" item. In Photo Library, User can select any images in Photo Album, and when user selects any image, Quality control will be shown (https://bugs.webkit.org/attachment.cgi?id=382225) and user can change target image quality (https://bugs.webkit.org/attachment.cgi?id=382226)
Got it, thanks.
Just curious if this is something that might be resolved soon?
I just tested again on iOS 13.5.1 If you select the 'Actual Size' option, it appears that the orientation information is correctly retained. But if you select any other option (Large, Medium or Small) the image has an incorrect orientation. This issue, combined with this one https://bugs.webkit.org/show_bug.cgi?id=207088, make photo uploads from iOS practically useless. Is this a Safari problem or a Webkit problem?
Neither; this problem exists in another system framework.
The fix for this issue was needed outside the WebKit project, therefore this is being resolved as 'Moved'. This is not yet fixed in shipping software.