W3C home > Mailing lists > Public > whatwg@whatwg.org > November 2013

Re: [whatwg] The src-N proposal

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Mon, 18 Nov 2013 12:40:56 -0800
Message-ID: <CAAWBYDBuDfVD65ACBX=gsEhJ8aSqtk34_kbWodnd9JOxJ=JApQ@mail.gmail.com>
To: Yoav Weiss <yoav@yoav.ws>
Cc: James Graham <james@hoppipolla.co.uk>, WHAT Working Group <whatwg@lists.whatwg.org>, Jonas Sicking <jonas@sicking.cc>
On Mon, Nov 18, 2013 at 12:32 PM, Yoav Weiss <yoav@yoav.ws> wrote:
> On Mon, Nov 18, 2013 at 8:58 PM, Jonas Sicking <jonas@sicking.cc> wrote:
>> On Mon, Nov 18, 2013 at 2:40 AM, James Graham <james@hoppipolla.co.uk>
>> wrote:
>> > This ugliness creates real issues e.g. if I have src-1, src-2 [...] and I
>> > decide I want a rule that is consulted between src-1 and src-2, I need to
>> > rewrite all my attribute names. Whilst this might produce a pleasant
>> rush of
>> > nostalgia for children of the 80s brought up on 8-bit Basic, for everyone
>> > else it seems like an error-prone drag.
>>
>> So all we need to do is to define that you don't have to use a
>> continuous numbered set. I.e. skipping numbers would be allowed.
>>
>> So people can do
>> <img src-10="..." src-20="...">
>>
>> Then if you need to insert a attribute, you simply do
>>
>> <img src-10="..." src-15="..." src-20="...">
>
> That is actually already part of the spec (implicitly), for that exact
> reason.

Well, not for that reason, but it does allow that usage if you want.

(I did it because it's an authoring hazard if deleting an attribute
means all src-Ns with higher numbers get ignored.)

~TJ
Received on Monday, 18 November 2013 20:41:43 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 17:00:14 UTC