[css-snappoints] Converting issue p tags to bikeshed-like format

Author: ChumpChief

css-snappoints/Overview.bs

@@ -14,9 +14,7 @@ Abstract: This module contains features to control panning and scrolling behavio
 Ignored Terms: scroll-snap-positions-*, containing block chain
 </pre>
 
-<p class="issue">
-    <b>This spec is currently undergoing major changes in line with the resolutions in <a href="https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html">https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html</a>. During this process it is not safe to assume that the current form will be representative of what it will look like in the future. After the work in process is completed, it will closely resemble <a href="https://drafts.csswg.org/css-scroll-snap/">this proposal</a>.</b>
-</p>
+Issue: <b>This spec is currently undergoing major changes in line with the resolutions in <a href="https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html">https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html</a>. During this process it is not safe to assume that the current form will be representative of what it will look like in the future. After the work in process is completed, it will closely resemble <a href="https://drafts.csswg.org/css-scroll-snap/">this proposal</a>.</b>
 
 <h2 id="intro">Introduction</h2>
 
@@ -185,7 +183,8 @@ Ignored Terms: scroll-snap-positions-*, containing block chain
         <dt><dfn export>snap alignment container</dfn>
         <dd>
             A scroll container's snap alignment container is the rectangle obtained by reducing its visual viewport by its 'scroll-snap-padding'.
-            <p class="issue">Better name for this concept?</p>
+
+            Issue: Better name for this concept?
 
         <dt><dfn lt="scroll snap margin" local-lt="snap margin" export>snap margin</dfn>
         <dd>
@@ -200,9 +199,7 @@ Ignored Terms: scroll-snap-positions-*, containing block chain
 
     The 'scroll-snap-type' property defines how strictly a <a>scroll container's</a> visual viewport should rest on <a>snap positions</a>.  It intentionally does not specify nor mandate any precise animations or physics used to enforce those snap positions; this is left up to the user agent.
 
-    <p class="issue">
-        <a href="https://lists.w3.org/Archives/Public/www-style/2015Nov/0328.html">Open issue</a> on whether to enhance the scroll-snap-type property for specifying the axis or adding a second property.  We have <a href="https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html">resolved</a> that this functionality be added once the issue is resolved.
-    </p>
+    Issue: <a href="https://lists.w3.org/Archives/Public/www-style/2015Nov/0328.html">Open issue</a> on whether to enhance the scroll-snap-type property for specifying the axis or adding a second property.  We have <a href="https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html">resolved</a> that this functionality be added once the issue is resolved.
 
     <pre class='propdef'>
     Name: scroll-snap-type
@@ -288,9 +285,7 @@ Ignored Terms: scroll-snap-positions-*, containing block chain
 
     The 'scroll-snap-align' property specifies how a scroll container's region specified by 'scroll-snap-padding' should align with descendent elements' scroll snap margin.  The two values specify the snapping behavior in the x and y axes, respectively.  If only one value is specified, the second value defaults to the same value.
 
-    <p class="issue">
-        Should this be x/y axes, or inline/block?  Starting with x/y axes for consistency with padding/area, otherwise a writing mode change would result in a axis mismatch (since padding is physical by default).
-    </p>
+    Issue: Should this be x/y axes, or inline/block?  Starting with x/y axes for consistency with padding/area, otherwise a writing mode change would result in a axis mismatch (since padding is physical by default).
 
     <pre class="propdef">
     Name: scroll-snap-align

css-snappoints/Overview.html

@@ -85,8 +85,6 @@ <h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="cont
      <dd><a href="http://www.w3.org/TR/css-snappoints-1/">http://www.w3.org/TR/css-snappoints-1/</a>
      <dt>Feedback:
      <dd><span><a href="mailto:www-style@w3.org?subject=%5Bcss-snappoints%5D%20YOUR%20TOPIC%20HERE">www-style@w3.org</a> with subject line “<kbd>[css-snappoints] <i data-lt="">… message topic …</i></kbd>” (<a href="http://lists.w3.org/Archives/Public/www-style/" rel="discussion">archives</a>)</span>
-     <dt>Issue Tracking:
-     <dd><a href="#issues-index">Inline In Spec</a>
      <dt class="editor">Editors:
      <dd class="editor p-author h-card vcard"><span class="p-name fn">Matt Rakow</span> (<span class="p-org org">Microsoft</span>)
      <dd class="editor p-author h-card vcard"><span class="p-name fn">Jacob Rossi</span> (<span class="p-org org">Microsoft</span>)
@@ -172,7 +170,7 @@ <h2 class="no-num no-toc no-ref" id="contents">Table of Contents</h2>
    </ol>
   </nav>
   <main>
-   <p class="issue" id="issue-752e30a5"><a class="self-link" href="#issue-752e30a5"></a> <b>This spec is currently undergoing major changes in line with the resolutions in <a href="https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html">https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html</a>. During this process it is not safe to assume that the current form will be representative of what it will look like in the future. After the work in process is completed, it will closely resemble <a href="https://drafts.csswg.org/css-scroll-snap/">this proposal</a>.</b> </p>
+   <p class="issue" id="issue-752e30a5"><a class="self-link" href="#issue-752e30a5"></a> <b>This spec is currently undergoing major changes in line with the resolutions in <a href="https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html">https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html</a>. During this process it is not safe to assume that the current form will be representative of what it will look like in the future. After the work in process is completed, it will closely resemble <a href="https://drafts.csswg.org/css-scroll-snap/">this proposal</a>.</b></p>
    <h2 class="heading settled" data-level="1" id="intro"><span class="secno">1. </span><span class="content">Introduction</span><a class="self-link" href="#intro"></a></h2>
    <p><em>This section is not normative.</em></p>
    <p>Popular UX paradigms for scrollable content frequently employ paging through content,
@@ -294,15 +292,15 @@ <h2 class="heading settled" data-level="4" id="definitions"><span class="secno">
     <dt><dfn data-dfn-type="dfn" data-export="" id="snap-alignment-container">snap alignment container<a class="self-link" href="#snap-alignment-container"></a></dfn> 
     <dd>
       A scroll container’s snap alignment container is the rectangle obtained by reducing its visual viewport by its <a class="property" data-link-type="propdesc" href="#propdef-scroll-snap-padding">scroll-snap-padding</a>. 
-     <p class="issue" id="issue-1b6eda6b"><a class="self-link" href="#issue-1b6eda6b"></a>Better name for this concept?</p>
+     <p class="issue" id="issue-1b6eda6b"><a class="self-link" href="#issue-1b6eda6b"></a> Better name for this concept?</p>
     <dt><dfn data-dfn-type="dfn" data-export="" data-local-lt="snap margin" data-lt="scroll snap margin" id="scroll-snap-margin">snap margin<a class="self-link" href="#scroll-snap-margin"></a></dfn> 
     <dd> An element’s snap margin is the rectangle obtained by expanding its border box by its <a class="property" data-link-type="propdesc" href="#propdef-scroll-snap-margin">scroll-snap-margin</a>. 
     <dt><dfn data-dfn-type="dfn" data-export="" data-local-lt="snap position" data-lt="scroll snap position" id="scroll-snap-position">snap position<a class="self-link" href="#scroll-snap-position"></a></dfn> 
     <dd> For a scroll container, a particular value for its scroll offset is a snap position if when scrolled to that offset the visual viewport of the scroll container would align with a descendent element in the manner specified by the scroll snap properties. 
    </dl>
    <h2 class="heading settled" data-level="5" id="scroll-snap-type"><span class="secno">5. </span><span class="content">Scroll Snap Types: the <a class="property" data-link-type="propdesc" href="#propdef-scroll-snap-type">scroll-snap-type</a> property</span><a class="self-link" href="#scroll-snap-type"></a></h2>
    <p>The <a class="property" data-link-type="propdesc" href="#propdef-scroll-snap-type">scroll-snap-type</a> property defines how strictly a <a data-link-type="dfn" href="#scroll-container">scroll container’s</a> visual viewport should rest on <a data-link-type="dfn" href="#scroll-snap-position">snap positions</a>.  It intentionally does not specify nor mandate any precise animations or physics used to enforce those snap positions; this is left up to the user agent.</p>
-   <p class="issue" id="issue-7e0cf181"><a class="self-link" href="#issue-7e0cf181"></a> <a href="https://lists.w3.org/Archives/Public/www-style/2015Nov/0328.html">Open issue</a> on whether to enhance the scroll-snap-type property for specifying the axis or adding a second property.  We have <a href="https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html">resolved</a> that this functionality be added once the issue is resolved. </p>
+   <p class="issue" id="issue-7e0cf181"><a class="self-link" href="#issue-7e0cf181"></a> <a href="https://lists.w3.org/Archives/Public/www-style/2015Nov/0328.html">Open issue</a> on whether to enhance the scroll-snap-type property for specifying the axis or adding a second property.  We have <a href="https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html">resolved</a> that this functionality be added once the issue is resolved.</p>
    <table class="def propdef" data-link-for-hint="scroll-snap-type">
     <tbody>
      <tr>
@@ -423,7 +421,7 @@ <h2 class="heading settled" data-level="7" id="scroll-snap-margin0"><span class=
    <p>This property is a shorthand property that sets all of the <a class="property" data-link-type="propdesc">scroll-snap-margin-*</a> longhands in one declaration.</p>
    <h2 class="heading settled" data-level="8" id="scroll-snap-align"><span class="secno">8. </span><span class="content">Scroll Snap Align: the <a class="property" data-link-type="propdesc" href="#propdef-scroll-snap-align">scroll-snap-align</a> property</span><a class="self-link" href="#scroll-snap-align"></a></h2>
    <p>The <a class="property" data-link-type="propdesc" href="#propdef-scroll-snap-align">scroll-snap-align</a> property specifies how a scroll container’s region specified by <a class="property" data-link-type="propdesc" href="#propdef-scroll-snap-padding">scroll-snap-padding</a> should align with descendent elements' scroll snap margin.  The two values specify the snapping behavior in the x and y axes, respectively.  If only one value is specified, the second value defaults to the same value.</p>
-   <p class="issue" id="issue-f7391e31"><a class="self-link" href="#issue-f7391e31"></a> Should this be x/y axes, or inline/block?  Starting with x/y axes for consistency with padding/area, otherwise a writing mode change would result in a axis mismatch (since padding is physical by default). </p>
+   <p class="issue" id="issue-f7391e31"><a class="self-link" href="#issue-f7391e31"></a> Should this be x/y axes, or inline/block?  Starting with x/y axes for consistency with padding/area, otherwise a writing mode change would result in a axis mismatch (since padding is physical by default).</p>
    <table class="def propdef" data-link-for-hint="scroll-snap-align">
     <tbody>
      <tr>
@@ -686,10 +684,10 @@ <h2 class="no-num heading settled" id="property-index"><span class="content">Pro
   </div>
   <h2 class="no-num heading settled" id="issues-index"><span class="content">Issues Index</span><a class="self-link" href="#issues-index"></a></h2>
   <div style="counter-reset:issue">
-   <div class="issue"> <b>This spec is currently undergoing major changes in line with the resolutions in <a href="https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html">https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html</a>. During this process it is not safe to assume that the current form will be representative of what it will look like in the future. After the work in process is completed, it will closely resemble <a href="https://drafts.csswg.org/css-scroll-snap/">this proposal</a>.</b> <a href="#issue-752e30a5"> ↵ </a></div>
-   <div class="issue">Better name for this concept?<a href="#issue-1b6eda6b"> ↵ </a></div>
-   <div class="issue"> <a href="https://lists.w3.org/Archives/Public/www-style/2015Nov/0328.html">Open issue</a> on whether to enhance the scroll-snap-type property for specifying the axis or adding a second property.  We have <a href="https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html">resolved</a> that this functionality be added once the issue is resolved. <a href="#issue-7e0cf181"> ↵ </a></div>
-   <div class="issue"> Should this be x/y axes, or inline/block?  Starting with x/y axes for consistency with padding/area, otherwise a writing mode change would result in a axis mismatch (since padding is physical by default). <a href="#issue-f7391e31"> ↵ </a></div>
+   <div class="issue"> <b>This spec is currently undergoing major changes in line with the resolutions in <a href="https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html">https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html</a>. During this process it is not safe to assume that the current form will be representative of what it will look like in the future. After the work in process is completed, it will closely resemble <a href="https://drafts.csswg.org/css-scroll-snap/">this proposal</a>.</b><a href="#issue-752e30a5"> ↵ </a></div>
+   <div class="issue"> Better name for this concept?<a href="#issue-1b6eda6b"> ↵ </a></div>
+   <div class="issue"> <a href="https://lists.w3.org/Archives/Public/www-style/2015Nov/0328.html">Open issue</a> on whether to enhance the scroll-snap-type property for specifying the axis or adding a second property.  We have <a href="https://lists.w3.org/Archives/Public/www-style/2015Dec/0048.html">resolved</a> that this functionality be added once the issue is resolved.<a href="#issue-7e0cf181"> ↵ </a></div>
+   <div class="issue"> Should this be x/y axes, or inline/block?  Starting with x/y axes for consistency with padding/area, otherwise a writing mode change would result in a axis mismatch (since padding is physical by default).<a href="#issue-f7391e31"> ↵ </a></div>
   </div>
  </body>
 </html>