-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Safari broken images and Image Resizer #3111
Comments
@dustinp26 If you know your F12 debug, then some infos regarding what URLs are being called which then fail would also be helpful. |
Those image url's I pasted in the original issue still present the issue and are what is being called. Not sure if you have Safari available to you but here is a loom video showing what occurs: https://www.loom.com/share/69062dbb8a1b408baf6d691c139131cd?sid=028c2d55-b26d-4e5c-acc1-5567b5e6ffa9 |
Thanks for the video! this is very strange and I'm not even sure how we could escalate this to ImageFlow (the makers of this). Could you try a few more things?
|
in 16.02/16.03 we updated the image-resizer. Could you check if this is still the case? |
Per your list above, # 3 which i mention at bottom of this response is where i might have something to help or perhaps this is what you already discovered and maybe fixed in 16.03/.03. 1 and 2 above I mention too in case there is anything you see that helps. If the blog on 2sxc.org is now running the 16.02/.03 then yes it is still an issue, otherwise I need to get one of those versions installed to test and Ill report back then. per your suggestions above:
4.10 KB Request Response Query String Parameters #3 - I think you have something here. If I pull up in firefox or chrome, download the image, it then will give me error as broken file but oddly I CAN open it up in chrome or firefox fine but not other programs for images like photoshop or preview. |
Just for understanding: the image on this page (when looking at this page in safari) also fails? Just to verify that we should be able to reproduce the problem just looking at this page... |
Yes, here is a screenshot of it in safari.
If I download image in 2 above it will not be a damaged image when saved to my computer and opens. The files size is 8kb vs 4kb if there is any relation to when an image gets to be too small in file size it breaks in safari (wild guess only). To further provide info - this image in safari works when width is sized down to 254 but begins to break at 253. Now this varies from image to image so it is not always a set width that breaks it for each image. Lastly, info from each image download from firefox that renders but two of them don't in safari and both of those end up broken images when downloaded. Notes the Bytes one says is 8kb on disk (the one that works) but the other two say 4kb but yet the bytes are just under 4100. Also notice the "Where from" under more info on the two broken ones - don''t know why the (2) gets added to this URL at the end as that is. |
Reported to ImageFlow here: https://github.com/imazen/imageflow/issues/635 |
I'm submitting a
[x] bug report => search github for a similar issue before submitting
...about
[x] Razor templating
Current Behavior / Expected Behavior
Safari will break the image if you are resizing it down a certain amount. It is not always the same and don't know what exactly causes it as some images will render fine and others not.
For instance, this image on the 2sxc blog when sized down to 100px wide breaks:
https://2sxc.org/portals/0/adam/blog%20app/rbvwi4qakukfunyjedfo4g/image/towelday%202sxc.jpg?mode=max&scale=both&quality=60&w=100
yet this works at 300px wide:
https://2sxc.org/portals/0/adam/blog%20app/rbvwi4qakukfunyjedfo4g/image/towelday%202sxc.jpg?mode=max&scale=both&quality=60&w=300
Ironically after discovering this, the 2sxc blog seemed to add the format=webp and those seem to work fine.
So this works: https://2sxc.org/portals/0/adam/blog%20app/rbvwi4qakukfunyjedfo4g/image/towelday%202sxc.jpg?mode=max&scale=both&format=webp&quality=60&w=100
Image would show in Safari
Not sure how or if this applies to 2sxc or more a Safari / imazen issue but figured i would report it.
Your environment
The text was updated successfully, but these errors were encountered: