[whatwg] Features for responsive Web design
Odin Hørthe Omdal
odinho at opera.com
Wed May 16 06:15:43 PDT 2012
Henri Sivonen <hsivonen at iki.fi> wrote:
> The what's currently in the spec is terribly counter-intuitive in this
The spec has a bug where it is contradicting itself in some steps. That
makes it very hard to read and confusing for those who read those steps.
>> I can see now how it does handle the art-direction case as well. I
>> think it's a shame that it's a different syntax to media queries but on
>> the plus side, if it maps directly to imgset in CSS, that's good.
> It seems to me that Media Queries are appropriate for the
> art-direction case and factors of the pixel dimensions of the image
> referred to by src="" are appropriate for the pixel density case.
Yes, the late load (or extra load). And the early load.
> I'm not convinced that it's a good idea to solve these two axes in the
> same syntax or solution. It seems to me that srcset="" is bad for the
> art-direction case and <picture> is bad for the pixel density case.
Weeeell. Not too sure I agree with /all/ of that. I agree in general,
but I also think that the early load model should be allowed to fetch
based on viewport size straight away.
If I have to choose between "loading image late, when mq etc engine has
started, being very flexible" and "loading image fast, not flexible at
all, just browser magic" - I'd go for the second one.
Even though we want to serve small images to my mobile phone, I'd still
like for it to be as fast as the browser is able to handle.
But it is merely meant for different sizes of the same content image
then. Only doing pixel densities feels very limiting. A bit too limiting
to be useful for the non-art directed "I just want it to go fast".
Odin Hørthe Omdal (Velmont/odinho) · Core, Opera Software, http://opera.com
More information about the whatwg