Progressive JPEGs: a new best practice

Re:Progressive JPEGs: a new best practice by DCoder on Sunday December 30, 2012 @05:06AM (#4985289)

If you specify width and height explicitly, certain browsers will have issues resizing them (if you set max-width: 100%, Chrome will squish a larger image horizontally but leave the height as it was, IE will scale it proportionally).

[ Parent | on HN ]

Re:Progressive JPEGs: a new best practice by TazeTSchnitzel on Sunday December 30, 2012 @05:21AM (#4985324)

I think that's because Chrome treats width= and height= as if they were CSS. (have a look at the inspector on an element with width and height specified in the HTML)

[ Parent | on HN ]

Re:Progressive JPEGs: a new best practice by DCoder on Sunday December 30, 2012 @06:28AM (#4985418)

That makes sense (thank you, don't know why I didn't realize that myself), but if I override that with css height: auto; , the browser no longer reserves space for the image while loading it... quite unfortunate.

[ Parent | on HN ]

Re:Progressive JPEGs: a new best practice by TazeTSchnitzel on Sunday December 30, 2012 @06:32AM (#4985425)

Maybe you should submit a WebKit (or possibly Chromium if this is Chrome-specific) bug for this.

[ Parent | on HN ]