[whatwg] Implementation complexity with elements vs an attribute (responsive images)
mat at matmarquis.com
Sun May 13 12:20:54 PDT 2012
On May 13, 2012, at 1:01 PM, Benjamin Hawkes-Lewis <bhawkeslewis at googlemail.com> wrote:
> On Sun, May 13, 2012 at 5:21 PM, Mathew Marquis <mat at matmarquis.com> wrote:
>>> AND they have to update their sites and mediaqueries when we get
>>> something new to optimize for. I don't think they will do that, based on
>>> how extremely big the problem with -webkit-prefixes are.
>>> I've seen enough of the web to be sceptical.
>> The amount of “developers can never be trusted with this” sentiment I’ve heard from the members of this group is incredibly depressing.
> That it depresses you does not mean that taking a more optimistic
> viewpoint will produce specifications that will result in better
> end-user experiences.
>> When we get “something new to optimize for,” we start adding that thing going forward. The evolution of media queries—or, say, HTML5—hasn’t led to a need to constantly revisit every piece of client work a developer has ever produced.
> In the case of webkit prefixes, authors have needed to update their
> work, have failed to do so, and now user agents are having to support
> webkit prefixes.
> The key problem about designing a responsive images solution around
> user agent characteristics not image characteristics is that authors
> will inevitably make more false assumptions about what images match
> what user agent characteristics than user agents will. As a result,
> user agents may be forced to misinterpret media queries in order to
> provide their users with better user experiences.
Correct me if I’m wrong, but wouldn’t this same reasoning apply to layouts that depend heavily on media queries?
The primary characteristics in play are screen size and resolution. I doubt any UAs will be forced to misinterpret common media queries because they haven’t been accounted for. I doubt UAs could, in fact—or would care. It wouldn’t be a matter of neglecting to support their product. It would be a matter of neglecting to supporting a screen at 310px wide.
This is to say nothing of the fact that the objective of a responsive layout _is_ to properly accommodate the widest possible range of displays. The things you’re trying to prevent are the things we’re trying to avoid anyway.
> What authors _can_ do and user agents _cannot_ do is describe their
> images. Such metadata never needs to be misinterpreted and allows user
> agents to iterate and improve the end-user experience even when the
> author either does not care about them, or has moved on, or is long
> dead. Is authors not caring about user agents a real problem?
> Certainly is - witness Opera's failed efforts to get authors to
> support more than Webkit, witness the widespread inaccessibility of
> web services, etc.
> Depressing but true.
> Benjamin Hawkes-Lewis
More information about the whatwg