[whatwg] The src-N proposal

Jirka Kosek jirka at kosek.cz
Mon Nov 18 07:34:25 PST 2013

On 18.11.2013 14:38, Marcos Caceres wrote:

> we really need to, srcset. The developer community already made
> significant sacrifices in compromising on picture because of issues
> that implementers raised about nested elements

Are those issues with nested elements described somewhere? I wasn't able
to find anything and I would really like to know what the issue was.

> of constituencies. Let’s not further erode those principles for the
> sake of markup aesthetics.

It's not just about aesthetics. From markup point of view src-n goes
against common sense and principles. Existing APIs and languages for
working with markup don't have easy way to access src-n attributes,
especially if order based on "n" is significant. This is very different
from nested elements where it's very easy to iterate over them.

Try to write JS+DOM, or XPath, or ... your preferred language here ...
code for looping through src-n attributes in a right order. Compare it
to the same code for subelements, which are ordered and have same name.


  Jirka Kosek      e-mail: jirka at kosek.cz      http://xmlguru.cz
       Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 rep.
    Bringing you XML Prague conference    http://xmlprague.cz

More information about the whatwg mailing list