[whatwg] <imgset> responsive imgs proposition (Re: The src-N proposal)

[Tab Atkins Jr.]

[whatever mail program you're using is doing quoting terribly, so I
have to correct it afterwards]

On Fri, Nov 15, 2013 at 3:42 PM, Timothy Hatcher <timothy at apple.com> wrote:
> On Nov 15, 2013, at 3:23 PM, Tab Atkins Jr. <jackalmage at gmail.com> wrote:
>> Not really.  PreloaderCSS gives you two choices, both bad:
>>
>> 1. Put the image sources in a <style> next to each <img>, thus
>> repeating your layout breakpoints in the MQs multiple times. (This
>> weakness is shared by src-N.)
>
> Addressed by attr() as mentioned in other replies already.

Not quite, as I addressed in those replies.  It helps, but it's
hacking around the issue by inverting it - rather than pushing the
definition of an MQ out to everywhere that needs it, it's pulling
everything that needs an MQ into the one definition of it.

>> The repetition is in the MQs, and that's solveable quite directly and
>> generically with custom MQs.
>
> And those custom MQs would need to be declared in a <style> inline to be
> useable by the preloader. So they will need to be declared inline and used
> in external CSS already. So why not take a more CSS approach instead of
> src-N if you already need to use a <style> to reduce repetition of MQs?

The two concepts aren't directly connected.  The fact that you're
using MQs for something doesn't intrinsically imply that the thing
should be CSS as well.  MQs are useful for plenty of things!

That's not an argument *for* src-N, of course.  It's just not an
argument against, either; it's a non sequitur for the current
discussion.

~TJ