New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 638525 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 9
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Progressive JPEGs are not rendered progressively when opened directly

Reported by inian1...@gmail.com, Aug 17 2016

Issue description

UserAgent: 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)
 
Cc: rnimmagadda@chromium.org
Labels: Needs-Feedback
Unable to repro this issue on MAC (10.11.6) for Google Chrome Stable Version - 52.0.2743.116

Screen-recording is attached.

@inian1234: Could you please re-test the same on a clean profile [chrome://settings -> Add Person -> Do not login] and let us know your observations.

Also, update your Google Chrome to Latest Stable Version - 52.0.2743.116

Thank you.
638525.mov
5.5 MB Download

Comment 3 by inian1...@gmail.com, 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

Comment 4 by mmenke@chromium.org, Aug 18 2016

Components: -Internals>Network Blink>Image
Labels: -Needs-Feedback
Status: Untriaged (was: Unconfirmed)
Confirmed in M52 stable and M54 canary on macOS.
Owner: schenney@chromium.org
Status: Available (was: Untriaged)
Components: -Blink>Image Internals>Images>Codecs
Labels: Needs-Feedback
Owner: ----
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.
Status: Untriaged (was: Available)
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

Labels: -Needs-Feedback
Owner: schenney@chromium.org
Status: Assigned (was: Untriaged)
Cc: scroggo@chromium.org fmalita@chromium.org vmi...@chromium.org
Components: Blink>Image
Owner: ----
Status: Available (was: Assigned)
Thanks for the new content. I'll route this to engineers with more experience in this area.
Project Member

Comment 12 by sheriffbot@chromium.org, Oct 5 2017

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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
Status: Available (was: Untriaged)
Oops, should have archived the pages that are now gone.
Labels: -Hotlist-Recharge-Cold BugSource-User PaintTeamTriaged-20171005
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. 

Comment 16 by f...@opera.com, Oct 6 2017

If you are able to just attach one of the (progressive) images to this bug, that would probably be fine too.
Project Member

Comment 17 by sheriffbot@chromium.org, Oct 8

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
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
Status: WontFix (was: Untriaged)
Still missing reproduction images. Re-open the bug if they become available.
@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.
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