News for hackers. Stuff that matters.
Re:Progressive JPEGs: a new best practice by pbhjpbhj on Saturday December 29, 2012 @03:42PM (#4983373)
>and progressive jpegs quickly stake out their territory and refine (or at least that’s the idea) //

Your browser stakes out the image area if you set height and width attributes for the image thus avoiding reflows.

Also the bracketed comment makes it sound like this feature doesn't work well?

Re:Progressive JPEGs: a new best practice by aerobson on Saturday December 29, 2012 @03:50PM (#4983405)
I have observed that even when you set height and width attributes, the area is not always "staked-out." Of course we'd assume that it is. I'll need to get you some browser and version details about this.
Re:Progressive JPEGs: a new best practice by codeka on Saturday December 29, 2012 @08:22PM (#4984136)
Are you saying if you specify <img width="xx" height="xx"> that the browser doesn't reserve exactly the right amount of space for that image? Because that's exactly what it's supposed to do: if it's not, then it's a browser bug.
Re:Progressive JPEGs: a new best practice by aerobson on Sunday December 30, 2012 @10:26AM (#4985909)
Update: this must have been my imagination. I confirmed that all of the most common browsers will stake out the image area if height and width is set in the css or the img tag.