[whatwg] So if media-queries aren't for determining the media to be used what are they for?
Anselm Hannemann Web Development
info at anselm-hannemann.com
Tue May 15 15:11:20 PDT 2012
Tab, maybe you think this is a good type to write the syntax but the majority of normal web developers are used to use common HTML syntax. This is why we proposed the picture element and normal attributes using media queries.
Of course this means we have lot more to write but at least this is intuitive and totally clear as it uses common structure of HTML. Do you agree with this?
I think it is more important that everyone understands the syntax and actually will use it instead of having a shorthand code that no one will use...?
Am 15.05.2012 um 23:56 schrieb Tab Atkins Jr.:
> On Tue, May 15, 2012 at 2:46 PM, Bruce Lawson <brucel at opera.com> wrote:
>> 1) the 600w 200h bit replicates the functionality of the familiar Media
>> Queries syntax but in a new unfamiliar microsyntax which many have argued is
>> ugly, unintuitive and prone to error
>> I'm sympathetic to (2); why require a developer to think of and describe
>> every permutation if the environment, when she could instead describe that
>> which she knows - the images - and then allow the UA to take the decision.
>> As time goes on, UAs get cleverer, so behaviour improves without the markup
>> needing changing.
>> But it doesn't seem necessary to saddle authors with (1) to acheive (2), as
>> far as I can see.
> I think I more or less agree with you. However, when you look at MQ,
> literally the only things you want to decide on are width/height, and
> *maybe* grayscale/color. You really don't need to be generic here, so
> you might as well optimize the syntax to make it easier to type.
> I think this is too much, personally. I'd prefer more verbosity here, like:
> <img src=foo.jpg srcset="foo-big.jpg min-width:1000px, foo-big at 2.jpg
> min-width:1000px 2x">
> Importantly, I think I'd like to be able to use either min or max, but
> @srcset's microsyntax only talks about min sizes. (I got it wrong in
> my previous email.)
More information about the whatwg