W3C home > Mailing lists > Public > whatwg@whatwg.org > January 2014

Re: [whatwg] Adding obsolete elements/attributes to indexes

From: Simon Sapin <simon.sapin@exyr.org>
Date: Thu, 23 Jan 2014 09:00:31 -0800
Message-ID: <52E14AAF.2020704@exyr.org>
To: Ian Hickson <ian@hixie.ch>
Cc: whatwg@lists.whatwg.org
On 23/01/2014 08:54, Ian Hickson wrote:
> On Thu, 23 Jan 2014, Simon Sapin wrote:
>>
>> To help with "discoverability" of obsolete features by implementers, IĘd
>> like them to be included in the Index sectionĘs tables.
>
> They're explicitly excluded to help with avoiding their discovery by
> authors.

I see. I still wish there was a version of the indexes for implementers :)


> There's a link from any interface that has obsolete IDL members to the
> partial interface that defines those members. As far as non-obsolete
> elements go, I think the only requirements in the obsolete section are
> regarding these obsolete IDL members.
>
>
>> When considering what Servo should implement, I mistakenly concluded
>> that <li> elements do not have a 'type' attribute, based on the Index.
>> They in fact do, as specified in the Obsolete features section.
>
> Do you mean a type IDL attribute or a type content attribute? No IDL
> attributes are listed in the index. I don't know what it really means for
> an element to have a content attribute, from an implement's persective.

IĘm talking about HTML attributes. In this case <li type=A>Foo</i> 
affecting rendering compared to just <li>Foo</li>.

Perhaps "elements having an attribute" is not the right term, but "a 
content attribute having meaning for the UA"?

-- 
Simon Sapin
Received on Thursday, 23 January 2014 17:01:14 UTC

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