Re: MWABP: Revised text for Device Capability Detection.

There is obviously a place for client side adaptation, per css media queries, indeed that's kind of what this document is about ... But we've previously discussed lack of general support for media queries, with the exception of Opera, I think, and we've previously noted that bunging everthing into one doc and letting the browser sort it out, can be, well, sub-optimal.

I haven't really thought about this much, but do css media queries play nicely with scripting? Don't you have the problem that you can't be sure what the browser has done or is about to do about applying the rules? Wouldn't you be better off doing it in script so you know where you are?


--- original message ---
From: "Adam Connors" <>
Subject: Re: MWABP: Revised text for Device Capability Detection.
Date: 22nd June 2009
Time: 9:18:02 am

> I tried to give examples of the type of adaption possible but they haven't
> made it into the draft
> How about
> "CSS Media Queries: Media queries allow developers to apply style rules
> depending on certain attributes of the device. See Media Queries [CSSMQ].
> For adaptation that requires reformatting of layout, fonts, background
> images, colours or hiding elements from mobile devices, this may be the
> simplest method for the developer"
> or some such?
> bruce

Apologies for that, Bruce, I was probably over zealous with the trimming. I
like the text you give here and will update the draft.

re: Chaal's question:

> More to the point, this calls into question the strength of "prefer server
> side techniques". While it is clear that those are more powerful, and can
> reduce the amount of content sent to the client, they are more complicated
> and are not necessarily available.

Isn't the difference here that we're talking about Web *applications* rather
than simple content. That you can modify layout etc with stylesheets is kind
of taken as read. We should probably call this out more explicitly.

Received on Monday, 22 June 2009 08:50:19 UTC