Spec document has wrong header level for classes and properties

HydraCG / Specifications

Specifications created by the Hydra W3C Community Group

Other

138 stars 26 forks source link

Spec document has wrong header level for classes and properties #78

Open RubenVerborgh opened 9 years ago

RubenVerborgh commented 9 years ago

The generated lists of classes and properties start out with two <h2> elements, but the remaining elements are <h3>. This results in an incorrect structure:

The respec-w3c-extensions.js script correctly generates <h3> elements, but ReSpec changes (only) the first two of them to <h2>. Since I'm not familiar enough with ReSpec to know which one is to blame, I decided to post it here. Tried looking for a fix, but didn't find a satisfactory one right away (subsection numbers started to appear).

akuckartz commented 9 years ago

The ReSpec community has been quite active recently (including an interesting discussion regarding support for RDFa :-). I suggest to enter an issue there: https://github.com/w3c/respec/issues

RubenVerborgh commented 9 years ago

I'm not sure whether it is a ReSpec issue or a problem with the custom JavaScript that is used to generate the Hydra spec.

lanthaler commented 9 years ago

I think this is a ReSpec bug. I just filed a bug.

alien-mcl commented 5 years ago

I think this can be closed without any actions. It seems the spec displays heads properly (Classes is a bit larger than actual class names) specscreenshot

tpluscode commented 5 years ago

Indeed, I don't see a problem with current doc. The header is <h2> and its sub-points are <h3>.

My vote to close

akuckartz commented 5 years ago

According to https://github.com/w3c/respec/issues/386#issuecomment-71359609 it was not a ReSpec issue.

alien-mcl commented 5 years ago

This would mean that the issue is random I was neither able to reproduce in any attempt, nor to find that getJSON async call that was mentioned in the respec issue. This issue is 3 years old and I'm keen to close it. Any objections?