News for hackers. Stuff that matters.

A comment on Faster Images using HTTP2 and Progressive JPEGs. Parent comment

Re:Faster Images using HTTP2 and Progressive JPEGs by hinkley on Wednesday December 28, 2016 @12:45PM (#13272138)
This is why I use vh, vw for proportional images at mobile breakpoints.

You still have to know the aspect ratio of the original image of course, but it does help.

[ Parent | on HN ]
Re:Faster Images using HTTP2 and Progressive JPEGs by eknkc on Thursday December 29, 2016 @02:48AM (#13276185)
We decided not use use viewport relative units for some reason I can't remember. I guess we had paddings etc in pixels and that would mean using calc() and that's another can of worms.

On a second thought, cw, ch as in container width, height would be a great addition.

[ Parent | on HN ]
Re:Faster Images using HTTP2 and Progressive JPEGs by patates on Thursday December 29, 2016 @05:27AM (#13276622)
> On a second thought, cw, ch as in container width, height would be a great addition.

Isn't that achieved by just defining height and width in percentages?

[ Parent | on HN ]
Re:Faster Images using HTTP2 and Progressive JPEGs by eknkc on Thursday December 29, 2016 @06:33AM (#13276789)
This would allow `height: 50cw`. Then we can define specific aspect ratios like `width: 100cw; height: 50cw;` would force image to have 2:1 aspect ratio.
[ Parent | on HN ]