- From: Attiks <attiks@gmail.com>
- Date: Mon, 27 Oct 2014 20:37:27 +0100
- To: Simon Pieters <simonp@opera.com>
- Cc: Ben Callahan <ben@heysparkbox.com>, "public-respimg@w3.org" <public-respimg@w3.org>
Received on Monday, 27 October 2014 19:37:54 UTC
Simon, I guess you're right, but that means that you always need to specify a fix width when using sizes to avoid the above stated problem. I'll give it some more thought and get back in a couple of days On Mon, Oct 27, 2014 at 7:55 AM, Simon Pieters <simonp@opera.com> wrote: > On Mon, 27 Oct 2014 17:45:46 +0200, Attiks <attiks@gmail.com> wrote: > > Simon, >> >> Yes, I meant vw >> >> You're right adding (min-width: 1060px) 424px will solve my problem, but >> it >> is not really easy. I expected it to work without out, and I guess most >> people will. Thank god element queries are on the way ;-) >> > > I'm not sure element queries will help for sizes. Since element queries > inherently need to know the layout, they can't be evaluated by the time > <img> wants to fetch a resource (i.e. potentially before CSS has loaded). > If we're OK with deferring the load of the image (with lazyload or so), > sizes would not be needed at all. > > > -- > Simon Pieters > Opera Software >
Received on Monday, 27 October 2014 19:37:54 UTC