Many thanks to everybody who has responded and for a lively and a productive
discussion!
Quick clarification: the proposal is to include *device* capabilities in the
HTTP headers, so when we say screen width and height we mean device screen
width and height which is constant (but can have
Boris,
if you don't mind me saying it, I am afraid you may be missing the point of
this request. In Responsive Web Design, device capabilities are used in a
high-level fashion to determine a class of the device: smartphone, tablet,
desktop. There is no need for exact viewport state. All the
Boris,
fair enough.
Two use-cases off of my head that do not currently have a non-ugly solution and
could if browsers reported device class:
1. Adaptive images:
To optimize user-experience on smart-phones (most of which have relatively
small screens, and are on slow connections most of the
Mathew,
thanks for raising that point.
I think we need to decide whether markup-based solution is a workaround forced
on us because there was no good solution or whether it is a solution we should
pursue, if implemented properly.
And this brings us to a very technical discussion about
