W3C home > Mailing lists > Public > public-respimg@w3.org > June 2013

[public-respimg] <none>

From: Mohsen Nabiloo Azimi <msnazi@gmail.com>
Date: Thu, 27 Jun 2013 10:47:51 -0700
Message-ID: <CAKbji+tQjWCZN-R8KrcJQBB=XfODL+qtNUBeBp46q1=3FwZ1LQ@mail.gmail.com>
To: public-respimg@w3.org
Pardon my lack of research if I'm bringing up something that is already
discussed. I've looked around but didn't see anything like what I have in
mind in archives.

This is how I see responsive images problem in current web:

We want one image in markup but that image should work great in large
screens, small screens and screens with high DPI. At the same time, we
might change image size and even image crop dependent on viewport width,
orientation or media type.

I think browsers can take care of this problem with progressive image
loading technologies that are available for WebP and JPEG. How? By
following this simple rule:

Load enough pixels to satisfy current view of image in current screen.

Web developer would put a <img tag with source to the largest image
they have. Browser will determine how much of that image should be
downloaded based on how that image is presented in web page.

For example, if an image is 2000 by 2000 pixels, but it's resized to 200
by 200 pixels, browser would not download whole image and scale it down.
It will actually just download enough pixels to cover the area that
image is covering. And likewise, if image is sized to 300 by 300 pixels
browser would download that much "pixels".

Have anybody thought about this before?

Mohsen <http://mohsenweb.com>
Received on Friday, 28 June 2013 07:47:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:06:09 UTC