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 9472 - deal with broken links in dynamic author view of spec by prompting users to choose to switch to full view
Summary: deal with broken links in dynamic author view of spec by prompting users to c...
Status: CLOSED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-10 01:18 UTC by Michael[tm] Smith
Modified: 2010-10-04 13:56 UTC (History)
4 users (show)

See Also:

Attachments

Description Michael[tm] Smith 2010-04-10 01:18:50 UTC 
<MikeSmith> Hixie: for the dynamic case, maybe one of your scripts
could cause an alert to pop up, saying "The target of this link is
not in the author view, do you want to switch to the full
(implementor) view instead?"  
<MikeSmith> or something like that  
<MikeSmith> I don't know how feasible that would be, though  
<Hixie> ooh that's a good idea  
<Hixie> MikeSmith: can you file a bug to that effect?  
<MikeSmith> Hixie: yeah, will do  

...the full context of the original IRC discussion:

<MikeSmith> Hixie: about the broken links in IDLs in the the
author view of the spec, for the static W3C copy of the
author-view that I'm generating, I guess I can have the script for
that rewrite the fragment IDs in the IDLs so that they point to
the domintro stuff instead, but not clear to me if/how it's
fixable in the dynamic/JS-switchable view of the spec  
<MikeSmith> and since not all attributes in the IDLs have
corresponding domintro content, I guess on I can just have the
build of the static author view un-link them and instead just
display them as normal text  
<MikeSmith> It seems like that's mainly the case for DOM
attributes that have same names as content attributes  
<MikeSmith> or whatever they're currently called in the spec to
distinguish them from one another  
<Hixie> MikeSmith: yeah i don't know what to do in the dynamic case  
<MikeSmith> if you need a schema to use for validation, the right
thing to use these days is either RelaxNG or W3C XML Schema  
<Hixie> MikeSmith: in the static case it might make more sense to
start from the pre-anolis draft, change the domintro elements to
dfn, and rerun anolis  
<MikeSmith> Hixie: for the dynamic case, maybe one of your scripts
could cause an alert to pop up, saying "The target of this link is
not in the author view, do you want to switch to the full
(implementor) view instead?"  
<MikeSmith> or something like that  
<MikeSmith> I don't know how feasible that would be, though  
<Hixie> ooh that's a good idea  
<Hixie> MikeSmith: can you file a bug to that effect?  
<MikeSmith> Hixie: yeah, will do
Comment 1 Ian 'Hixie' Hickson 2010-04-13 08:09:12 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: Accepted
Change Description: see diff given below
Rationale: Concurred with reporter's comments.