[css-2017] Several issues of the indices

[xfq]

The indices in Snapshot 2017 have several issues:

1. The Selector Index is empty.

2. @font-face and @import do not appear in the At-Rule Index, although css-fonts-3 and css-cascade-3 are present in Overview.bs.

3. There are two index sections:

• https://www.w3.org/TR/2017/NOTE-css-2017-20170131/#indices
• https://www.w3.org/TR/2017/NOTE-css-2017-20170131/#index

Should the two sections above be put together? If so, is it technically feasible (with the current Bikeshed)?

---

/cc @frivoal @tabatkins

[frivoal]

There are two index sections:

https://www.w3.org/TR/2017/NOTE-css-2017-20170131/#indices
https://www.w3.org/TR/2017/NOTE-css-2017-20170131/#index

Should the two sections above be put together?

I wonder if it wouldn't be just as well to discard the second one entirely. I am not convinced it is terribly useful in this document, and if it is a cause of confusion due to the presence of the full indices, maybe we're better off without it.

[frivoal]

The Selector Index is empty.

@font-face and @import do not appear in the At-Rule Index, although css-fonts-3 and css-cascade-3 are present in Overview.bs.

I have no idea what's causing this. Bikeshed is reporting success without any error or warning, but clearly something is wrong. @tabatkins ?

[plinss]

FWIW, both @font-face and @import are in the anchor database and appear to have the proper attributes (at-rule type, exported, etc), so it's not a spec markup issue.

[SelenIT]

Properties and values from CSS UI (like outline, box-sizing and link to it from the content-box value etc.) also seem to be missing from the indices. Doesn't this issue has something to do with naming pattern change ('css3-ui'/'css-ui-3' etc.)?

[svgeesus]

@Keyframes is also missing

[frivoal]

@tabatkins Can you figure out what Bikeshed is doing wrong (or what I did to make it do the wrong thing)?

[frivoal]

@tabatkins ping.

[xfq]

https://drafts.csswg.org/indexes/ looks more complete.

[frivoal]

@tabatkins This continues to affect the 2018 snapshot, and I have no idea what's wrong.