- From: Peter Linss via GitHub <sysbot+gh@w3.org>
- Date: Fri, 19 May 2017 23:26:33 +0000
- To: public-css-archive@w3.org
In the past we've preferred linking tests to the most specific anchor in the spec. The spec anchor database (available via json api from shepherd) allows tooling to identify which sections those anchors are in (as used in shepherd and the older test harness). Also note that anchors tend to move into different sections, often with section # differences between the draft and /TR, some tests also link to the draft vs the /TR version of a spec. I favor keeping the spec links more specific and having the tooling map the anchors to sections, rather than shift the tests to more coarse-grained linking. -- GitHub Notification of comment by plinss Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1395#issuecomment-302832411 using your GitHub account
Received on Friday, 19 May 2017 23:26:40 UTC