[issuegen] Process headings

Author: fantasai

bin/issuegen.pl

@@ -143,6 +143,24 @@
 while (<IN>) {
   chomp;
 
+  # Process headings
+  if (/^=/) {
+    s/=//g;
+    s/^\s+|\s+$//g ;
+    s/\{\s*(.+?)\s*\}//;
+    my $headerID;
+    if ($1) {
+      $headerID = $1;
+      $headerID =~ s/^#//;
+    }
+    else {
+      $headerID = lc;
+      $headerID =~ s/\s+/-/g;
+    }
+    print OUT "<h2 id=$headerID>" . $_ . "</h2>\n";
+    next;
+  }
+
   # Don't pipe code
   s/</&lt;/g;
 

css-scroll-snap/issues-by-issue.html

@@ -34,8 +34,7 @@ <h1>CSS Scroll Snapping Level 1 Disposition of Comments for 2015-03-26 WD</h1>
 <p>An issue can be closed as <code>Accepted</code>, <code>OutOfScope</code>,
 <code>Invalid</code>, <code>Rejected</code>, or <code>Retracted</code>.
 <code>Verified</code> indicates commentor's acceptance of the response.</p>
-<h2 id=> Scroll Snapping Geometry 
-</h2>
+<h2 id=scroll-snapping-geometry>Scroll Snapping Geometry</h2>
 <pre class=' a' id='issue-1'>
 <span>Issue 1. <a href='#issue-1'>#</a></span>
 <span>Summary:  Snapping should be element-based</span>
@@ -201,8 +200,7 @@ <h2 id=> Scroll Snapping Geometry
 <span>Summary:  Should apply to more than just block-level boxes</span>
 <span>  <a href='https://lists.w3.org/Archives/Public/www-style/2014Feb/0607.html'>https://lists.w3.org/Archives/Public/www-style/2014Feb/0607.html</a> (dbaron)</span>
 <span>Open: Make it apply to all non-inlines? everything?</span></pre>
-<h2 id=> Scroll Snapping Triggers 
-</h2>
+<h2 id=scroll-snapping-triggers>Scroll Snapping Triggers</h2>
 <pre class='open ' id='issue-20'>
 <span>Issue 20. <a href='#issue-20'>#</a></span>
 <span>Summary:  Define that scroll gestures don't snap "backwards"</span>
@@ -301,8 +299,7 @@ <h2 id=> Scroll Snapping Triggers
 <span>    Some convenience APIs might be useful,</span>
 <span>    e.g. to compute the possible snapping destinations</span>
 <span>    when scrolling in a particular direction.</span></pre>
-<h2 id=> Syntax and Property Interactions 
-</h2>
+<h2 id=syntax-and-property-interactions>Syntax and Property Interactions</h2>
 <pre class=' ' id='issue-40'>
 <span>Issue 40. <a href='#issue-40'>#</a></span>
 <span>Summary:  Use flow-relative logical syntax</span>
@@ -450,8 +447,7 @@ <h2 id=> Syntax and Property Interactions
 <span>Summary:  Have the children determine the scroll snapping beahvior (proximity, mandatory), rather than container.</span>
 <span>  <a href='https://lists.w3.org/Archives/Public/www-style/2014Feb/0607.html'>https://lists.w3.org/Archives/Public/www-style/2014Feb/0607.html</a> (Seattle F2F)</span>
 <span>Open: =TF= Discuss</span></pre>
-<h2 id=> Scroll Snapping Behavior 
-</h2>
+<h2 id=scroll-snapping-behavior>Scroll Snapping Behavior</h2>
 <pre class='open ' id='issue-https://lists.w3.org/Archives/Public/www-style/2013Aug/0249.html'>
 <span>Issue 60</span>
 <span>Summary:  Add scroll jumping feature</span>
@@ -567,8 +563,7 @@ <h2 id=> Scroll Snapping Behavior
 <span>Issue 72</span>
 <span>Summary:  Define that snap point defined by element is triggered when targetting fragment of element</span>
 <span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Oct/0164.html'>https://lists.w3.org/Archives/Public/www-style/2015Oct/0164.html</a></span></pre>
-<h2 id=> Enabling Element-based Snappoints 
-</h2>
+<h2 id=enabling-element-based-snappoints>Enabling Element-based Snappoints</h2>
 <pre class=' a' id='issue-80'>
 <span>Issue 80. <a href='#issue-80'>#</a></span>
 <span>Summary:  Remove "scroll-snap-position-x/y:elements"</span>
@@ -629,8 +624,8 @@ <h2 id=> Enabling Element-based Snappoints
 <span>    What element captures abspos snappoints?</span>
 <span>    Response: (rakow) Should use containing block chain, but need term</span>
 <span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Jun/0376.html'>https://lists.w3.org/Archives/Public/www-style/2015Jun/0376.html</a></span></pre>
-<pre class=' ' id='issue-https://lists.w3.org/Archives/Public/www-style/2015Jul/0453.html'>
-<span>Issue 83</span>
+<pre class=' ' id='issue-83'>
+<span>Issue 83. <a href='#issue-83'>#</a></span>
 <span>Summary:  Adding back elements would make snap-points-x/y exclusive with element-based points</span>
 <span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Jun/0376.html'>https://lists.w3.org/Archives/Public/www-style/2015Jun/0376.html</a> (rakow)</span>
 <span>    if we add back the elements value then I'd rather go back to making</span>
@@ -639,8 +634,7 @@ <h2 id=> Enabling Element-based Snappoints
 <span>    Are there really no merged use cases?</span>
 <span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Jul/0453.html'>https://lists.w3.org/Archives/Public/www-style/2015Jul/0453.html</a> (rakow)</span>
 <span>    Can't think of a single one</span></pre>
-<h2 id=> Errors 
-</h2>
+<h2 id=errors>Errors</h2>
 <pre class=' a' id='issue-90'>
 <span>Issue 90. <a href='#issue-90'>#</a></span>
 <span>Summary:  Reference to box, doesn't say whether margin/padding/content box</span>