Set maxTocLevel=2 properly with fix from respec
authorsspeiche
Thu, 23 Jan 2014 08:52:53 -0500
changeset 443 02e1a65a8776
parent 439 28beff0a4f89
child 444 2cde3822d20f
Set maxTocLevel=2 properly with fix from respec
ldp.html
--- a/ldp.html	Wed Jan 22 17:18:36 2014 -0500
+++ b/ldp.html	Thu Jan 23 08:52:53 2014 -0500
@@ -31,8 +31,7 @@
       For the three scripts below, if your spec resides on dev.w3 you can check them
       out in the same tree and use relative links so that they'll work offline,
      -->
-  <script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove' async></script> 
- <!--    <script src='file:///Users/sspeiche/git/respec/js/profile-w3c-common.js' class='remove' async></script>  -->  
+    <script src='https://www.w3.org/Tools/respec/respec-w3c-common' class='remove' async></script> 
     <script class='remove'>
       var respecConfig = {
           // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
@@ -65,7 +64,7 @@
           lcEnd: "2013-09-02",
           
           // Only include h1 and h2 level
-          maxTocLevel: 0, // HACK: We want 2 but auto-numbering doesn't happen
+          maxTocLevel: 2,
 
           // if you want to have extra CSS, append them to this list
           // it is recommended that the respec.css stylesheet be kept