I'd contest that it is no harder to understand than it is to understand why your CSS behaves differently when a JS element acts on the mark-up. We are used to one stack defining how another acts. We do it all the time. Adding classes to mark-up to control display, or just the cascade on its own does this.
Is this harder to understand than <picture> or srcset is what really matters. Anything we do to resolve this resource adaption problem will by necessity complicate things. Is this better than the alternatives? Remember too that this idea can be mixed with existing techniques, it is not a replacement for other ways of dealing with stuff. You'd be free to bake your media-queries into CSS in exactly the same way as you do now, if a sub-module didn't want to respond to a generic breakpoint, for example. -Matt On 14 May 2012 11:01, Anne van Kesteren <ann...@annevk.nl> wrote: > On Mon, May 14, 2012 at 10:55 AM, Matthew Wilcox <m...@matthewwilcox.com> > wrote: >> have any of you seen this proposal for an alternative solution to the >> problem? >> >> http://www.w3.org/community/respimg/2012/05/13/an-alternative-proposition-to-and-srcset-with-wider-scope/ >> >> I like the general idea and from an author perspective this seems >> great; but I know nothing of the browser/vendor side of the equation - >> is this do-able? > > Adding a level of indirection is actually not that great as it makes > it harder to understand what is going on. Also if you work on sites in > teams it's not always a given access to <head> is equal to the > templates that are being authored. Let alone full control over how > resources are stored. > > > -- > Anne — Opera Software > http://annevankesteren.nl/ > http://www.opera.com/
