Skip to content

Commit

Permalink
[css-scroll-snap] Update changes, add DoC
Browse files Browse the repository at this point in the history
  • Loading branch information
fantasai committed May 17, 2017
1 parent 2e09eaa commit a20645e
Show file tree
Hide file tree
Showing 3 changed files with 191 additions and 4 deletions.
32 changes: 28 additions & 4 deletions css-scroll-snap/Overview.bs
Original file line number Diff line number Diff line change
Expand Up @@ -1058,10 +1058,34 @@ Acknowledgements {#acknowledgements}
Changes {#changes}
==================

Changes since the <a href="https://www.w3.org/TR/2016/WD-css-scroll-snap-1-20160623/">23 June 2016 Working Draft</a> include:
Changes since the <a href="https://www.w3.org/TR/2016/CR-css-scroll-snap-1-20161020/">20 October 2016 Candidate Recommendation</a> include:

<ul>
<li>Renamed 'scroll-padding' to 'scroll-padding' and extended its uses.
<li>Removed renaming issues because nobody came up with a better alternative to ''scroll-snap-type: mandatory | proximity'' or ''scroll-snap-stop: normal''.
<li>Miscellaneous clarifications.
<li>Restricting 'scroll-padding' to non-negative values.
(<a href="https://github.com/w3c/csswg-drafts/issues/1084">Issue 1084</a>)
<blockquote>
<p>Values <ins>must be non-negative and</ins>
are interpreted as for 'padding' &hellip;</p>
</blockquote>
<li>Clarifying that snapping in one axis may affect whether snapping to a particular snap area is possible in the other axis.
(<a href="https://github.com/w3c/csswg-drafts/issues/950">Issue 950</a>)
<blockquote>
<ins><p class="note">Although ''scroll-snap-type: both'' evaluates [=snap positions=] independently in each axis,
<a href="#choosing">choosing</a> of a [=snap position=] in one axis
may be influenced by [=snap positions=] in the other axis.
For example, snapping in one axis
may push off-screen the [=snap area=] that the other axis would otherwise align to,
making its [=snap position=] invalid and therefore unchooseable.</p></ins>
</blockquote>
<li>Clarifying that scroll snapping does not mandate any particular input method.
(<a href="https://github.com/w3c/csswg-drafts/issues/1305">Issue 1305</a>)
<blockquote>
<ins><p class="note">This specification only applies to scrolling methods supported by the user agent.
It does not require the user agent to support any particular input or scrolling method.</p></ins>
</blockquote>
<li>Fixed some syntax errors in examples and added a new one to the 'scroll-snap-type' section.
(<a href="https://github.com/w3c/csswg-drafts/issues/827">Issue 827</a>)
</ul>


A <a href="https://drafts.csswg.org/css-scroll-snap-1/issues-cr-2016">Disposition of Comments</a> is available.
49 changes: 49 additions & 0 deletions css-scroll-snap/issues-cr-2016.bsi
Original file line number Diff line number Diff line change
@@ -0,0 +1,49 @@
Draft: https://www.w3.org/TR/2016/CR-css-scroll-snap-1-20161020/
Title: CSS Scroll Snapping Level 1

----
Issue 1.
Summary: Examples and syntax of scroll-snap-type conflict
From: Wenson Hsieh
Comment: https://github.com/w3c/csswg-drafts/issues/827
Response: https://github.com/w3c/csswg-drafts/issues/827#issuecomment-269347510
Changes: https://github.com/w3c/csswg-drafts/commit/7a20d00238aac3ddbdd8d5dd7e74ff81dd29ba76
Closed: Accepted
Resolved: Editorial
----
Issue 2.
Summary: Clarify that css-scroll-snap doesn't dictate any particular input method
From: Benoit Girard
Comment: https://github.com/w3c/csswg-drafts/issues/1305
Response: https://github.com/w3c/csswg-drafts/issues/1305#issuecomment-301600041
Changes: https://github.com/w3c/csswg-drafts/commit/9760282d421c772b0e08b745149b8f7d21208ff1
Closed: Accepted
Resolved: Editorial
Verified: https://github.com/w3c/csswg-drafts/issues/1305#issuecomment-301938166
----
Issue 3.
Summary: Specify how scroll-padding expands out
From: Peter Linss
Comment: https://github.com/w3c/csswg-drafts/issues/1050
Response: https://github.com/w3c/csswg-drafts/issues/1050#issuecomment-301591832
Closed: Invalid
----
Issue 4.
Summary: Should negative scroll-padding be allowed
From: fantasai
Comment: https://github.com/w3c/csswg-drafts/issues/1084
Response: https://github.com/w3c/csswg-drafts/issues/1084#issuecomment-302153089
Changes: https://github.com/w3c/csswg-drafts/commit/8158a651b75e81db6dcbdffd17c91e3edb81de5d
Closed: Accepted
Resolved: CSSWG Telecon 2017-05-17
Verified: Reporter is editor
----
Issue 5.
Summary: Clarify how visibility requirement makes snap x/y snap positions interdependent
From: Majid Valipour
Comment: https://github.com/w3c/csswg-drafts/issues/950
Response: https://github.com/w3c/csswg-drafts/issues/950#issuecomment-301597661
Changes: https://hg.csswg.org/drafts/diff/ae445d9c2266/css-scroll-snap/Overview.bs
Closed: Accepted
Resolved: Editorial
----
114 changes: 114 additions & 0 deletions css-scroll-snap/issues-cr-2016.html
Original file line number Diff line number Diff line change
@@ -0,0 +1,114 @@
<!DOCTYPE html>
<meta charset="utf-8">
<title>CSS Scroll Snapping Level 1 Disposition of Comments for 2016-10-20 CR</title>
<style type="text/css">
pre { border: solid thin silver; padding: 0.2em; white-space: normal; }
pre > span { display: block; white-space: pre; }
:not(pre).a { background: lightgreen }
:not(pre).d { background: lightblue }
:not(pre).oi { background: yellow }
:not(pre).r { background: orange }
:not(pre).fo { background: red }
.open { border: solid red; }
:target { box-shadow: 0.25em 0.25em 0.25em; }
a[href^=mid], a[href~=flatten] { text-decoration: none; }
abbr { font-weight: bold; }
</style>

<h1>CSS Scroll Snapping Level 1 Disposition of Comments for 2016-10-20 CR</h1>

<p>Dated Draft: <a href="https://www.w3.org/TR/2016/CR-css-scroll-snap-1-20161020/">https://www.w3.org/TR/2016/CR-css-scroll-snap-1-20161020/</a>

<p>Editor's Draft: <a href="http://drafts.csswg.org/css-scroll-snap-1/">http://drafts.csswg.org/css-scroll-snap-1/</a>

<p>The following color coding convention is used for comments:</p>

<ul>
<li class="a">Accepted or Rejected and positive response
<li class="r">Rejected and no response
<li class="fo">Rejected and negative response
<li class="d">Deferred
<li class="oi">Out-of-Scope or Invalid and not verified
</ul>

<p class=open>Open issues are marked like this</p>

<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>
<pre class=' a' id='issue-1'>
<span>Issue 1. <a href='#issue-1'>#</a></span>
<span>Summary: Examples and syntax of scroll-snap-type conflict</span>
<span>From: Wenson Hsieh</span>
<span>Comment: <a href='https://github.com/w3c/csswg-drafts/issues/827'>https://github.com/w3c/csswg-drafts/issues/827</a></span>
<span>Response: <a href='https://github.com/w3c/csswg-drafts/issues/827#issuecomment-269347510'>https://github.com/w3c/csswg-drafts/issues/827#issuecomment-269347510</a></span>
<span>Changes: <a href='https://github.com/w3c/csswg-drafts/commit/7a20d00238aac3ddbdd8d5dd7e74ff81dd29ba76'>https://github.com/w3c/csswg-drafts/commit/7a20d00238aac3ddbdd8d5dd7e74ff81dd29ba76</a></span>
<span class="a">Closed: Accepted</span>
<span>Resolved: Editorial</span></pre>
<pre class=' a' id='issue-2'>
<span>Issue 2. <a href='#issue-2'>#</a></span>
<span>Summary: Clarify that css-scroll-snap doesn't dictate any particular input method</span>
<span>From: Benoit Girard</span>
<span>Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1305'>https://github.com/w3c/csswg-drafts/issues/1305</a></span>
<span>Response: <a href='https://github.com/w3c/csswg-drafts/issues/1305#issuecomment-301600041'>https://github.com/w3c/csswg-drafts/issues/1305#issuecomment-301600041</a></span>
<span>Changes: <a href='https://github.com/w3c/csswg-drafts/commit/9760282d421c772b0e08b745149b8f7d21208ff1'>https://github.com/w3c/csswg-drafts/commit/9760282d421c772b0e08b745149b8f7d21208ff1</a></span>
<span class="a">Closed: Accepted</span>
<span>Resolved: Editorial</span>
<span class="a">Verified: <a href='https://github.com/w3c/csswg-drafts/issues/1305#issuecomment-301938166'>https://github.com/w3c/csswg-drafts/issues/1305#issuecomment-301938166</a></span></pre>
<pre class=' oi' id='issue-3'>
<span>Issue 3. <a href='#issue-3'>#</a></span>
<span>Summary: Specify how scroll-padding expands out</span>
<span>From: Peter Linss</span>
<span>Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1050'>https://github.com/w3c/csswg-drafts/issues/1050</a></span>
<span>Response: <a href='https://github.com/w3c/csswg-drafts/issues/1050#issuecomment-301591832'>https://github.com/w3c/csswg-drafts/issues/1050#issuecomment-301591832</a></span>
<span class="oi">Closed: Invalid</span></pre>
<pre class=' a' id='issue-4'>
<span>Issue 4. <a href='#issue-4'>#</a></span>
<span>Summary: Should negative scroll-padding be allowed</span>
<span>From: fantasai</span>
<span>Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1084'>https://github.com/w3c/csswg-drafts/issues/1084</a></span>
<span>Response: <a href='https://github.com/w3c/csswg-drafts/issues/1084#issuecomment-302153089'>https://github.com/w3c/csswg-drafts/issues/1084#issuecomment-302153089</a></span>
<span>Changes: <a href='https://github.com/w3c/csswg-drafts/commit/8158a651b75e81db6dcbdffd17c91e3edb81de5d'>https://github.com/w3c/csswg-drafts/commit/8158a651b75e81db6dcbdffd17c91e3edb81de5d</a></span>
<span class="a">Closed: Accepted</span>
<span>Resolved: CSSWG Telecon 2017-05-17</span>
<span class="a">Verified: Reporter is editor</span></pre>
<pre class=' a' id='issue-5'>
<span>Issue 5. <a href='#issue-5'>#</a></span>
<span>Summary: Clarify how visibility requirement makes snap x/y snap positions interdependent</span>
<span>From: Majid Valipour</span>
<span>Comment: <a href='https://github.com/w3c/csswg-drafts/issues/950'>https://github.com/w3c/csswg-drafts/issues/950</a></span>
<span>Response: <a href='https://github.com/w3c/csswg-drafts/issues/950#issuecomment-301597661'>https://github.com/w3c/csswg-drafts/issues/950#issuecomment-301597661</a></span>
<span>Changes: <a href='https://hg.csswg.org/drafts/diff/ae445d9c2266/css-scroll-snap/Overview.bs'>https://hg.csswg.org/drafts/diff/ae445d9c2266/css-scroll-snap/Overview.bs</a></span>
<span class="a">Closed: Accepted</span>
<span>Resolved: Editorial</span></pre>
<script>
(function () {
var sheet = document.styleSheets[0];
function addCheckbox(className) {
var element = document.querySelector('*.' + className);
var span = document.createElement('span');
span.innerHTML = element.innerHTML;
element.innerHTML = null;
var check = document.createElement('input');
check.type = 'checkbox';
if (className == 'open') {
check.checked = false;
sheet.insertRule('pre:not(.open)' + '{}', sheet.cssRules.length);
check.onchange = function (e) {
rule.style.display = this.checked ? 'none' : 'block';
}
}
else {
check.checked = true;
sheet.insertRule('pre.' + className + '{}', sheet.cssRules.length);
check.onchange = function (e) {
rule.style.display = this.checked ? 'block' : 'none';
}
}
var rule = sheet.cssRules[sheet.cssRules.length - 1];
element.appendChild(check);
element.appendChild(span);
}
['a', 'd', 'fo', 'oi', 'r', 'open'].forEach(addCheckbox);
}());
</script>

0 comments on commit a20645e

Please sign in to comment.