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 9367 - fix broken links in IDLs by changing id references of hyperlinks in IDLs to point to content in domintro boxes instead of UA implementation details
Summary: fix broken links in IDLs by changing id references of hyperlinks in IDLs to p...
Status: CLOSED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-30 09:25 UTC by Michael[tm] Smith
Modified: 2010-10-04 14:46 UTC (History)
4 users (show)

See Also:

Attachments

Description Michael[tm] Smith 2010-03-30 09:25:19 UTC 
The targets of most (or all) links for attributes and method names, etc., in IDLs in the spec currently point to IDs that are in sections marked with "impl". Those sections get dropped from the author view ("Hide UA text" view) of the spec, which effectively results in breaking all the links.

The ID references for those IDL attributes, method names, etc., should instead by changed to point to the corresponding content in the domintro boxes (which are also included as part of the author view), so that the links are not broken for users of the author view.
Comment 1 Ian 'Hixie' Hickson 2010-04-03 02:22:38 UTC 
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document:
   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Rejected
Change Description: no spec change
Rationale: Those aren't the definitions, so it'd be wrong to point there. I'd love to find another solution though. Not sure what that would be though.