[css-scroll-snap] Update DoC

Author: fantasai

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

@@ -327,7 +327,8 @@ <h2 id=syntax-and-property-interactions>Syntax and Property Interactions</h2>
 <span>    Layout isn't always logical</span>
 <span>  <a href='https://lists.w3.org/Archives/Public/www-style/2013Aug/0258.html'>https://lists.w3.org/Archives/Public/www-style/2013Aug/0258.html</a> (howcome)</span>
 <span>    Axis isn't usually defined by writing mode, but direction within axis is</span>
-<span>Open</span></pre>
+<span class="a">Closed:   Accepted by TF</span>
+<span class="">Open:     =WG= Discuss</span></pre>
 <pre class=' a' id='issue-https://lists.w3.org/Archives/Public/www-style/2014Oct/0480.html'>
 <span>Issu 41.</span>
 <span>Summary:  Add "none" value to scroll-snap-points-x/y</span>
@@ -393,11 +394,15 @@ <h2 id=syntax-and-property-interactions>Syntax and Property Interactions</h2>
 <span>    (Scrolling through a vertical snapped list of items, but some might overflow.)</span>
 <span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Jun/0159.html'>https://lists.w3.org/Archives/Public/www-style/2015Jun/0159.html</a></span>
 <span>    Note: FF implements axis-separate snap-type</span>
-<span>Solution: For per-axis snap control, use per-axis alignment.</span>
-<span class="">Open:     Propose to close no change.</span>
-<span>          =WG= and =roc= Discuss whether nested scroller case is necessary.</span>
-<span>          i.e. horizontal scroller traps horizontal snaps while</span>
-<span>               vertical scroller ancestor traps vertical snaps</span></pre>
+<span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Oct/0213.html'>https://lists.w3.org/Archives/Public/www-style/2015Oct/0213.html</a></span>
+<span>    Requirements are threefold:</span>
+<span>      1. single-axis snapping</span>
+<span>      2. both-axis snapping</span>
+<span>      3. 2D snapping</span>
+<span>Solution: allow scroll-snap-align to specify one or both axis coordinates</span>
+<span>Solution: add [ x | y | block | inline | both | point ] keywords</span>
+<span class="a">Closed:   Accepted by TF</span>
+<span class="">Open:     =WG= Discuss and approve?</span></pre>
 <pre class=' a' id='issue-46'>
 <span>Issue 46. <a href='#issue-46'>#</a></span>
 <span>Summary:  Scroll-snap-coordinate needs x/y longhands</span>
@@ -565,14 +570,15 @@ <h2 id=scroll-snapping-behavior>Scroll Snapping Behavior</h2>
 <span>    Diagonally positioned snappable elements in a 2d scroller, for example snapping to center on cities on a map</span>
 <span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Jun/0170.html'>https://lists.w3.org/Archives/Public/www-style/2015Jun/0170.html</a></span>
 <span>    1D vs 2D snapping</span>
-<span class="">Open:  =TF= Discuss whether current solution is optimal</span></pre>
+<span class="a">Closed:   Accepted</span>
+<span class="">Open:     =WG= Discuss whether to defer</span></pre>
 <pre class='open ' id='issue-68'>
 <span>Issue 68. <a href='#issue-68'>#</a></span>
 <span>Summary:  Better definition of snapping behavior</span>
 <span>  <a href='https://lists.w3.org/Archives/Public/www-style/2014Oct/0474.html'>https://lists.w3.org/Archives/Public/www-style/2014Oct/0474.html</a> (roc)</span>
 <span>    Need more precise, consolidated definition of snapping behavior</span>
 <span>Solution: "Scroll Snapping Model" and "Scroll Snapping Mechanics" sections</span>
-<span class="a">Closed:   Accepted [by TF]</span>
+<span class="a">Closed:   Accepted by TF</span>
 <span class="">Open:     =roc= Review</span></pre>
 <pre class='open ' id='issue-69'>
 <span>Issue 69. <a href='#issue-69'>#</a></span>
@@ -597,7 +603,7 @@ <h2 id=scroll-snapping-behavior>Scroll Snapping Behavior</h2>
 <span>Solution: Snap to furthest valid scroll position</span>
 <span>          <a href='https://hg.csswg.org/drafts/diff/c283d8b6be5c/css-scroll-snap/Overview.bs'>https://hg.csswg.org/drafts/diff/c283d8b6be5c/css-scroll-snap/Overview.bs</a></span>
 <span>          <a href='https://hg.csswg.org/drafts/diff/a55dada6cbcb/css-scroll-snap/Overview.bs'>https://hg.csswg.org/drafts/diff/a55dada6cbcb/css-scroll-snap/Overview.bs</a></span>
-<span class="a">Closed:   Accepted</span></pre>
+<span class="a">Closed:   Accepted by TF</span></pre>
 <pre class=' a' id='issue-71'>
 <span>Issue 71. <a href='#issue-71'>#</a></span>
 <span>Summary:  Define what happens with snap points outside of scrollable area</span>
@@ -608,7 +614,7 @@ <h2 id=scroll-snapping-behavior>Scroll Snapping Behavior</h2>
 <span>    (Consider behavior when an element moves and its corresponding snappoint shifts slightly outside the scrollable area.)</span>
 <span>Solution: Specified that scroll-snap-points-x/y don't generate more than one repetition outside scrollable area;</span>
 <span>          Handle out-of-range snap positions as above (snap to furthest possible point).</span>
-<span class="a">Closed:   Accepted</span></pre>
+<span class="a">Closed:   Accepted by TF</span></pre>
 <pre class='open ' id='issue-https://lists.w3.org/Archives/Public/www-style/2015Oct/0164.html'>
 <span>Issue 72</span>
 <span>Summary:  Define that snap point defined by element is triggered when targetting fragment of element</span>
@@ -643,50 +649,42 @@ <h2 id=enabling-element-based-snappoints>Enabling Element-based Snappoints</h2>
 <pre class='open ' id='issue-82'>
 <span>Issue 82. <a href='#issue-82'>#</a></span>
 <span>Summary:  Trapping snap points</span>
-<span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015May/0282.html'>https://lists.w3.org/Archives/Public/www-style/2015May/0282.html</a> (NYC 2015)</span>
-<span>    Elements value is needed to trap scroll-snap contributions,</span>
-<span>    for cases where author decides to remove scrollability.</span>
-<span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Jun/0147.html'>https://lists.w3.org/Archives/Public/www-style/2015Jun/0147.html</a> (smfr)</span>
-<span>    Less sure about this now</span>
-<span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Mar/0153.html'>https://lists.w3.org/Archives/Public/www-style/2015Mar/0153.html</a></span>
-<span>    Layout affecting whether scrollbars appear can affect snapping containership</span>
-<span>    Response: (rakow) Switched to keying off of 'overflow' computed value</span>
-<span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Mar/0154.html'>https://lists.w3.org/Archives/Public/www-style/2015Mar/0154.html</a></span>
-<span>    Summary:  Need to consider 'overflow: hidden'</span>
-<span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Mar/0156.html'>https://lists.w3.org/Archives/Public/www-style/2015Mar/0156.html</a></span>
-<span>    Response: (rakow) Key off 'scroll' or 'auto'?</span>
-<span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Mar/0157.html'>https://lists.w3.org/Archives/Public/www-style/2015Mar/0157.html</a></span>
-<span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Jun/0147.html'>https://lists.w3.org/Archives/Public/www-style/2015Jun/0147.html</a></span>
-<span>    Nested scrollers issue -- need scrollers to trap snappoints</span>
-<span>    Response: (majid) Separate capture from snapping</span>
-<span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Jun/0159.html'>https://lists.w3.org/Archives/Public/www-style/2015Jun/0159.html</a></span>
-<span>    Response: (rakow) Need some way to specify capture, maybe "elements"?</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>
-<span>    Response: (majid) That doesn't prevent pass-through on scrollers.</span>
-<span>    Need to be associated to nearest scrollable ancestor, but only</span>
-<span>    snap if 'elements' is specified.</span>
-<span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Jul/0035.html'>https://lists.w3.org/Archives/Public/www-style/2015Jul/0035.html</a></span>
-<span>    Response: (rakow)</span>
-<span>    * Scrollability is defined by 'auto' or 'scroll' computed value</span>
-<span>    * Scrollability in an axis captures snappoints in that axis</span>
-<span>    * Do we really need snapping to pass through per axis?</span>
-<span>    * Priorities of nested snapping vs 2D snapping?</span>
-<span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Jul/0457.html'>https://lists.w3.org/Archives/Public/www-style/2015Jul/0457.html</a></span>
-<span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Jun/0148.html'>https://lists.w3.org/Archives/Public/www-style/2015Jun/0148.html</a></span>
+<span>   <a href='https://lists.w3.org/Archives/Public/www-style/2015May/0282.html'>https://lists.w3.org/Archives/Public/www-style/2015May/0282.html</a> (NYC 2015)</span>
+<span>     Elements value is needed to trap scroll-snap contributions,</span>
+<span>     for cases where author decides to remove scrollability.</span>
+<span>   <a href='https://lists.w3.org/Archives/Public/www-style/2015Jun/0147.html'>https://lists.w3.org/Archives/Public/www-style/2015Jun/0147.html</a> (smfr)</span>
+<span>     Less sure about this now..</span>
+<span>     Also, nested scrollers issue -- need scrollers to trap snappoints</span>
+<span>   <a href='https://lists.w3.org/Archives/Public/www-style/2015Jun/0159.html'>https://lists.w3.org/Archives/Public/www-style/2015Jun/0159.html</a> (majid)</span>
+<span>     Separate capture from snapping</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>     Need some way to specify capture, maybe "elements"?</span>
+<span>   <a href='https://lists.w3.org/Archives/Public/www-style/2015Jul/0035.html'>https://lists.w3.org/Archives/Public/www-style/2015Jul/0035.html</a> (majid)</span>
+<span>     That doesn't prevent pass-through on scrollers. Need to be associated</span>
+<span>     to nearest scrollable ancestor, but only snap if 'elements' is specified.</span>
+<span>   <a href='https://lists.w3.org/Archives/Public/www-style/2015Jul/0457.html'>https://lists.w3.org/Archives/Public/www-style/2015Jul/0457.html</a> (rakow)</span>
+<span>     * Scrollability is defined by 'auto' or 'scroll' computed value</span>
+<span>     * Scrollability in an axis captures snappoints in that axis</span>
+<span>     * Do we really need snapping to pass through per axis?</span>
+<span>     * Priorities of nested snapping vs 2D snapping?</span>
+<span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Oct/0211.html'>https://lists.w3.org/Archives/Public/www-style/2015Oct/0211.html</a> (fantasai + Tab)</span>
+<span>     Two issues:</span>
+<span>       1. Specifying that 'overflow'-based trapping either</span>
+<span>          A. In both axes</span>
+<span>          B. In scrollable axes</span>
+<span>       2. Allowing elements that aren't scroll containers to trap snap points;</span>
+<span>          suggest using 'scroll-snap-type' applied to all elements.</span>
 <span>Solution: Define that 'overflow: scroll/auto' in an axis captures snappoints either</span>
 <span>          A) In that axis</span>
 <span>          B) In both axes</span>
 <span>Solution: If needed, make scroll-snap-type on an element trap snappoints;</span>
 <span>          don't use scroll-snap-points-x/y</span>
-<span class="">Open:     =WG= Discuss, suggest resolving A vs. B plus scroll-snap-type trapment</span></pre>
-<pre class='open ' id='issue-83'>
+<span class="">Open:     =WG= Discuss whether nested scroller case is necessary.</span>
+<span>          i.e. horizontal scroller traps horizontal snaps while</span>
+<span>               vertical scroller ancestor traps vertical snaps</span>
+<span>          =WG= Resolve A vs. B plus scroll-snap-type trapment keywords</span></pre>
+<pre class=' ' id='issue-83'>
 <span>Issue 83. <a href='#issue-83'>#</a></span>
-<span>Summary: 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>
-<span class="">Open:    =TF= Needs clarification</span></pre>
-<pre class=' ' id='issue-84'>
-<span>Issue 84. <a href='#issue-84'>#</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>
@@ -729,6 +727,14 @@ <h2 id=errors>Errors</h2>
 <span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Jul/0075.html'>https://lists.w3.org/Archives/Public/www-style/2015Jul/0075.html</a></span>
 <span>Solution: Used value floored at UA-specified minimum, recommended at 1px.</span>
 <span class="a">Closed:   Accepted</span></pre>
+<pre class=' a' id='issue-94'>
+<span>Issue 94. <a href='#issue-94'>#</a></span>
+<span>Summary: What element captures abspos snappoints?</span>
+<span>  <a href='https://lists.w3.org/Archives/Public/www-style/2015Jun/0148.html'>https://lists.w3.org/Archives/Public/www-style/2015Jun/0148.html</a> (smfr)</span>
+<span>    Snap point capture should follow containing block chain</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>    Should use containing block chain, but need term...</span>
+<span class="a">Closed:   Accepted</span></pre>
 <script>
 (function () {
 	var sheet = document.styleSheets[0];