- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Tue, 20 Jun 2017 12:34:52 +0000
- To: public-css-archive@w3.org
Hmmm. Yes, it does solve that problem, but then it introduces another one instead: if it has the same shortname as media queries level 4, bikeshed considers that it replaces level 4 entirely, which is not true, since it is a diff spec which only contains the new bits, and leaves level 4 to define the rest. Applying your patch, bikeshed starts to complain about not finding definitions that level 5 refers to, but are defined in level 4. I get these errors for instance: ``` LINK ERROR: No 'dfn' refs found for 'media queries' that are marked for export. <a data-link-type="dfn" data-lt="Media Queries">Media Queries</a> LINK ERROR: No 'dfn' refs found for 'media feature' that are marked for export. <a data-link-type="dfn" data-lt="media feature">media feature</a> LINK ERROR: No 'type' refs found for '<media-query-list>' that are marked for export. <a class="production" data-link-type="type" data-lt="<media-query-list>"><media-query-list></a> LINK ERROR: No 'dfn' refs found for 'range context' that are marked for export. <a data-link-type="dfn" data-lt="range context">range context</a>``` @tabatkins What's the writing way to set up the spec so that bikeshed both generates the correct links (as with @tobie 's patch) AND keeps understanding links to things defined in the previous level (as with the spec as it is now)? -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/pull/1542#issuecomment-309739170 using your GitHub account
Received on Tuesday, 20 June 2017 12:34:58 UTC