It's a best practice because it gives the user as much possible as soon as possible, and because there are file size savings. When you say it would be better to have a placeholder there that is the same frame as the…
I never said baseline jpegs display instantly after file download. They render as I describe several times, top to bottom or "chop chop chop." It's progressive jpegs that display instantly after file download IF the…
Why do you say Preferably in the HTML? Just curious. I vaguely recall there was a reason.
Agreed. But would you say that progressive jpegs don't offer a visual advantage in this case? Imagine if a photo has a caption below it: baseline starts rendering far away from the caption, but with progressive we'll…
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.
Thanks for the comment. Whatever detail you can add to this conversation is much appreciated. It's a neglected topic, and it's important for us to understand it better.
Right?! This is very interesting and I just discovered it by chance. If it were just one browser we could write it off, but it's not. I'll try to find out.
This brings up some important points. Yes, we need numbers. Let's get them. Progressive jpegs do not necessarily need to use more RAM. The FAQ I linked to also says "If the data arrives quickly, a progressive-JPEG…
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.
What I'm digging about HireArt is that companies using it seem to be more organized. They think more about the position they are hiring for at the start, submit interview questions to HireArt, write better job…
It's a best practice because it gives the user as much possible as soon as possible, and because there are file size savings. When you say it would be better to have a placeholder there that is the same frame as the…
I never said baseline jpegs display instantly after file download. They render as I describe several times, top to bottom or "chop chop chop." It's progressive jpegs that display instantly after file download IF the…
Why do you say Preferably in the HTML? Just curious. I vaguely recall there was a reason.
Agreed. But would you say that progressive jpegs don't offer a visual advantage in this case? Imagine if a photo has a caption below it: baseline starts rendering far away from the caption, but with progressive we'll…
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.
Thanks for the comment. Whatever detail you can add to this conversation is much appreciated. It's a neglected topic, and it's important for us to understand it better.
Right?! This is very interesting and I just discovered it by chance. If it were just one browser we could write it off, but it's not. I'll try to find out.
This brings up some important points. Yes, we need numbers. Let's get them. Progressive jpegs do not necessarily need to use more RAM. The FAQ I linked to also says "If the data arrives quickly, a progressive-JPEG…
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.
What I'm digging about HireArt is that companies using it seem to be more organized. They think more about the position they are hiring for at the start, submit interview questions to HireArt, write better job…