Progressive JPEGs are not rendered progressively when opened directly
Reported by
inian1...@gmail.com,
Aug 17 2016
|
|||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36 Example URL: http://104.236.143.201/progressive.jpg Steps to reproduce the problem: 1. http://104.236.143.201/progressive.jpg is not rendered progressively. But if I include the same image as part of a HTML page, it is rendered progressively. For example, in http://104.236.143.201/test.html the image is progressively rendered as expected What is the expected behavior? Image should be progressively rendered even when I open the image URL directly. Firefox and Safari behave this way. What went wrong? The code which decodes the image progressively does not get triggered when you open the image directly? 🤔 Did this work before? N/A Chrome version: 52.0.2743.82 Channel: canary OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 22.0 r0 Enable connection throttling to a slower connection speed to see the progressive render (or lack thereof)
,
Aug 18 2016
,
Aug 18 2016
Hey, The image is rendering - just not progressively (layer by layer instead of top down). In this video I just made, the HTML page on the left renders it progressively, but when I open the same image referenced in the HTML page, it loads sequentially. (Ignore the page on the right half of the video) https://www.youtube.com/watch?v=oeQ0OhYspd0
,
Aug 18 2016
,
Aug 18 2016
Confirmed in M52 stable and M54 canary on macOS.
,
Aug 19 2016
,
Sep 14 2016
Back looking at this on a slow network, cache cleared etc. Reproduces for sure. I think that the difference between using it in am img tag and loading directly is that direct display of images resizes the image to fit in the viewport, whereas using it in an img tag uses the native size if none is given. To resize we probably need the complete image loaded before we display anything, hence bypassing the progressive nature of it. inian1234@, could you do one or both of the following for us to confirm the hypothesis: (a) try this with an image small enough to fit in the window without resizing and/or (b) see what happens when you use the existing image but give a size for the div that forces the image to resize (or use it as background image with background-size: cover or the like). As far as fixing it goes, all I can think to do is emit an image when each layer is decoded, but that seems complicated.
,
Sep 20 2016
,
Oct 3 2016
I created a page with progressive images small enough to fit the viewport (so that no re-sizing happens). However, I am still seeing the same issue.. Page - http://104.236.143.201/test_small.html Image - http://104.236.143.201/progressive_small.jpg
,
Oct 5 2016
,
Oct 5 2016
Thanks for the new content. I'll route this to engineers with more experience in this area.
,
Oct 5 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 5 2017
Oops, should have archived the pages that are now gone.
,
Oct 5 2017
,
Oct 6 2017
Hey schenney, sorry I didn't realise that I brought down the server. I can re-create the progressive versions of some image and upload it again on a server if it helps.
,
Oct 6 2017
If you are able to just attach one of the (progressive) images to this bug, that would probably be fine too.
,
Oct 8
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 9
Still missing reproduction images. Re-open the bug if they become available.
,
Oct 9
@schenney@chromium.org Pretty sure this is a dupe of https://bugs.chromium.org/p/chromium/issues/detail?id=884959, so it's already fixed.
,
Oct 10
Yup, confirmed with a progressive image (https://s3.amazonaws.com/inian-backup/ini1.jpg) that is rendering as expected when opened directly too. |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by rnimmagadda@chromium.org
, Aug 18 2016Labels: Needs-Feedback