[css-snappoints] Adding warning about spec trajectory per resolution https://logs.csswg.org/irc.w3.org/css/2016-01-13/#e635410

Author: ChumpChief

css-snappoints/Overview.bs

@@ -15,6 +15,10 @@ 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>
+
 <h2 id="intro">Introduction</h2>
 
     <em>This section is not normative.</em>

css-snappoints/Overview.html

@@ -114,7 +114,7 @@
   <div class="head">
    <p data-fill-with="logo"><a class="logo" href="http://www.w3.org/"> <img alt="W3C" height="48" src="https://www.w3.org/Icons/w3c_home" width="72"> </a> </p>
    <h1 class="p-name no-ref" id="title">CSS Scroll Snap Points Module Level 1</h1>
-   <h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="content">Editor’s Draft, <time class="dt-updated" datetime="2016-01-12">12 January 2016</time></span></h2>
+   <h2 class="no-num no-toc no-ref heading settled" id="subtitle"><span class="content">Editor’s Draft, <time class="dt-updated" datetime="2016-01-13">13 January 2016</time></span></h2>
    <div data-fill-with="spec-metadata">
     <dl>
      <dt>This version:
@@ -211,6 +211,7 @@ <h2 class="no-num no-toc no-ref heading settled" id="contents"><span class="cont
    </ul>
   </div>
   <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>
    <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,
@@ -506,22 +507,22 @@ <h2 class="no-num heading settled" id="acknowledgments"><span class="content">Ac
   <h2 class="no-ref no-num heading settled" id="conformance"><span class="content"> Conformance</span><a class="self-link" href="#conformance"></a></h2>
   <h3 class="heading settled" id="document-conventions"><span class="content"> Document conventions</span><a class="self-link" href="#document-conventions"></a></h3>
   <p>Conformance requirements are expressed with a combination of
-  descriptive assertions and RFC 2119 terminology. The key words "MUST",
-  "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
-  "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this
+  descriptive assertions and RFC 2119 terminology. The key words “MUST”,
+  “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”,
+  “RECOMMENDED”, “MAY”, and “OPTIONAL” in the normative parts of this
   document are to be interpreted as described in RFC 2119.
   However, for readability, these words do not appear in all uppercase
   letters in this specification. </p>
   <p>All of the text of this specification is normative except sections
   explicitly marked as non-normative, examples, and notes. <a data-link-type="biblio" href="#biblio-rfc2119">[RFC2119]</a> </p>
-  <p>Examples in this specification are introduced with the words "for example"
+  <p>Examples in this specification are introduced with the words “for example”
   or are set apart from the normative text with <code>class="example"</code>,
   like this: </p>
   <div class="example" id="example-52448c84">
    <a class="self-link" href="#example-52448c84"></a> 
    <p>This is an example of an informative example. </p>
   </div>
-  <p>Informative notes begin with the word "Note" and are set apart from the
+  <p>Informative notes begin with the word “Note” and are set apart from the
   normative text with <code>class="note"</code>, like this: </p>
   <p class="note" role="note">Note, this is an informative note. </p>
   <p>Advisements are normative sections styled to evoke special attention and are
@@ -722,6 +723,7 @@ <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"> <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>