Add mechanism to link to the ED #106
Labels
Comments
tidoust
added a commit
to tidoust/media-web-roadmap
that referenced
this issue
Jun 27, 2018
See w3c#106 3 new mechanisms to link to the Editor's Draft: 1. add a `data-linkto="ED"` attribute next to the `data-featureid` attribute to have the framework link to the Editor's Draf for that link 2. add a `linkto` property set to `ED` to the `toc.json` file to have the framework link to the Editor's Draft for all links in the prose. 3. define custom tables and set the `linkto` property of the `spec` column to `ED` to tell the framework to link to the Editor's Draft in the summary table. Note the update also fixes fragment handling when features are targeted (the URL of the feature was previously unused, meaning links always targeted the top of the spec, and not the relevant section when a feature was used).
xfq
pushed a commit
that referenced
this issue
Jun 28, 2018
See #106 3 new mechanisms to link to the Editor's Draft added: 1. add a `data-linkto="ED"` attribute next to the `data-featureid` attribute to have the framework link to the Editor's Draft for that link 2. add a `linkto` property set to `ED` to the `toc.json` file to have the framework link to the Editor's Draft for all links in the prose. 3. define custom tables and set the `linkto` property of the `spec` column to `ED` to tell the framework to link to the Editor's Draft in the summary table. Note the update also fixes fragment handling when features are targeted (the URL of the feature was previously unused, meaning links always targeted the top of the spec, and not the relevant section when a feature was used).
|
Now done. Check commit message and README for details. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue depends on #105.
While I think a link to the document in /TR/ is a good default for these roadmap documents, authors may want to link to the ED from time to time. We should put such a mechanism in place through some
data-attribute.For instance
<a data-featureid="css-backgrounds-3" data-version="ED"></a>The attribute could have another name. We should probably not have
data-ed="true"though, because default may change. People may find that the /TR/ vision is not good and that links should rather be to ED by default after all (this could perhaps even be a setting at the roadmap level)The text was updated successfully, but these errors were encountered: