This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 7638 - editorial: Add a pointer to the supplemental interface behind a class=impl for all interfaces that have a supplemental interface in this spec (in the obsolete section)
Summary: editorial: Add a pointer to the supplemental interface behind a class=impl fo...
Status: CLOSED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: LC
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-15 19:20 UTC by contributor
Modified: 2010-10-04 13:58 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2009-09-15 19:20:06 UTC 
Section: http://www.whatwg.org/specs/web-apps/current-work/#htmlanchorelement

Comment:
editorial: Add a pointer to the supplemental interface behind a class=impl for all interfaces that have a supplemental interface in this spec (in the obsolete section)

Posted from: 83.252.193.59
Comment 1 Ian 'Hixie' Hickson 2009-09-29 01:26:01 UTC 
There is one already. Just click the interface name, and if it links to the "12.3.4 Other elements, attributes and APIs" section, you know there's an obsolete bit to worry about. Generally though I don't want to raise the visibility of the obsolete section any more than that.
Comment 2 Simon Pieters 2009-09-29 10:56:29 UTC 
That only works in the WHATWG single-page version, not the multipage version or the W3C version. Also, it is not particularly discoverable; an implementor working on a feature is likely to completely miss the obsolete section.

It doesn't necessarily have to be a link, it could be just

<span class=impl>/* There are further members to this interface defined in supplemental interfaces */</span>

or something.
Comment 3 Ian 'Hixie' Hickson 2009-09-29 11:14:22 UTC 
Editing that would be a maintenance nightmare. I really don't want to go there. I don't buy that implementors are going to have that much trouble with this — in practice, most already have the obsolete section done, and the test suite will cover it, so new implementors will find out soon enough when they try to implement the spec.