Skip to content

Commit a20645e

Browse files
committed
[css-scroll-snap] Update changes, add DoC
1 parent 2e09eaa commit a20645e

3 files changed

Lines changed: 191 additions & 4 deletions

File tree

css-scroll-snap/Overview.bs

Lines changed: 28 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1058,10 +1058,34 @@ Acknowledgements {#acknowledgements}
10581058
Changes {#changes}
10591059
==================
10601060

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

10631063
<ul>
1064-
<li>Renamed 'scroll-padding' to 'scroll-padding' and extended its uses.
1065-
<li>Removed renaming issues because nobody came up with a better alternative to ''scroll-snap-type: mandatory | proximity'' or ''scroll-snap-stop: normal''.
1066-
<li>Miscellaneous clarifications.
1064+
<li>Restricting 'scroll-padding' to non-negative values.
1065+
(<a href="https://github.com/w3c/csswg-drafts/issues/1084">Issue 1084</a>)
1066+
<blockquote>
1067+
<p>Values <ins>must be non-negative and</ins>
1068+
are interpreted as for 'padding' &hellip;</p>
1069+
</blockquote>
1070+
<li>Clarifying that snapping in one axis may affect whether snapping to a particular snap area is possible in the other axis.
1071+
(<a href="https://github.com/w3c/csswg-drafts/issues/950">Issue 950</a>)
1072+
<blockquote>
1073+
<ins><p class="note">Although ''scroll-snap-type: both'' evaluates [=snap positions=] independently in each axis,
1074+
<a href="#choosing">choosing</a> of a [=snap position=] in one axis
1075+
may be influenced by [=snap positions=] in the other axis.
1076+
For example, snapping in one axis
1077+
may push off-screen the [=snap area=] that the other axis would otherwise align to,
1078+
making its [=snap position=] invalid and therefore unchooseable.</p></ins>
1079+
</blockquote>
1080+
<li>Clarifying that scroll snapping does not mandate any particular input method.
1081+
(<a href="https://github.com/w3c/csswg-drafts/issues/1305">Issue 1305</a>)
1082+
<blockquote>
1083+
<ins><p class="note">This specification only applies to scrolling methods supported by the user agent.
1084+
It does not require the user agent to support any particular input or scrolling method.</p></ins>
1085+
</blockquote>
1086+
<li>Fixed some syntax errors in examples and added a new one to the 'scroll-snap-type' section.
1087+
(<a href="https://github.com/w3c/csswg-drafts/issues/827">Issue 827</a>)
10671088
</ul>
1089+
1090+
1091+
A <a href="https://drafts.csswg.org/css-scroll-snap-1/issues-cr-2016">Disposition of Comments</a> is available.

css-scroll-snap/issues-cr-2016.bsi

Lines changed: 49 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,49 @@
1+
Draft: https://www.w3.org/TR/2016/CR-css-scroll-snap-1-20161020/
2+
Title: CSS Scroll Snapping Level 1
3+
4+
----
5+
Issue 1.
6+
Summary: Examples and syntax of scroll-snap-type conflict
7+
From: Wenson Hsieh
8+
Comment: https://github.com/w3c/csswg-drafts/issues/827
9+
Response: https://github.com/w3c/csswg-drafts/issues/827#issuecomment-269347510
10+
Changes: https://github.com/w3c/csswg-drafts/commit/7a20d00238aac3ddbdd8d5dd7e74ff81dd29ba76
11+
Closed: Accepted
12+
Resolved: Editorial
13+
----
14+
Issue 2.
15+
Summary: Clarify that css-scroll-snap doesn't dictate any particular input method
16+
From: Benoit Girard
17+
Comment: https://github.com/w3c/csswg-drafts/issues/1305
18+
Response: https://github.com/w3c/csswg-drafts/issues/1305#issuecomment-301600041
19+
Changes: https://github.com/w3c/csswg-drafts/commit/9760282d421c772b0e08b745149b8f7d21208ff1
20+
Closed: Accepted
21+
Resolved: Editorial
22+
Verified: https://github.com/w3c/csswg-drafts/issues/1305#issuecomment-301938166
23+
----
24+
Issue 3.
25+
Summary: Specify how scroll-padding expands out
26+
From: Peter Linss
27+
Comment: https://github.com/w3c/csswg-drafts/issues/1050
28+
Response: https://github.com/w3c/csswg-drafts/issues/1050#issuecomment-301591832
29+
Closed: Invalid
30+
----
31+
Issue 4.
32+
Summary: Should negative scroll-padding be allowed
33+
From: fantasai
34+
Comment: https://github.com/w3c/csswg-drafts/issues/1084
35+
Response: https://github.com/w3c/csswg-drafts/issues/1084#issuecomment-302153089
36+
Changes: https://github.com/w3c/csswg-drafts/commit/8158a651b75e81db6dcbdffd17c91e3edb81de5d
37+
Closed: Accepted
38+
Resolved: CSSWG Telecon 2017-05-17
39+
Verified: Reporter is editor
40+
----
41+
Issue 5.
42+
Summary: Clarify how visibility requirement makes snap x/y snap positions interdependent
43+
From: Majid Valipour
44+
Comment: https://github.com/w3c/csswg-drafts/issues/950
45+
Response: https://github.com/w3c/csswg-drafts/issues/950#issuecomment-301597661
46+
Changes: https://hg.csswg.org/drafts/diff/ae445d9c2266/css-scroll-snap/Overview.bs
47+
Closed: Accepted
48+
Resolved: Editorial
49+
----
Lines changed: 114 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,114 @@
1+
<!DOCTYPE html>
2+
<meta charset="utf-8">
3+
<title>CSS Scroll Snapping Level 1 Disposition of Comments for 2016-10-20 CR</title>
4+
<style type="text/css">
5+
pre { border: solid thin silver; padding: 0.2em; white-space: normal; }
6+
pre > span { display: block; white-space: pre; }
7+
:not(pre).a { background: lightgreen }
8+
:not(pre).d { background: lightblue }
9+
:not(pre).oi { background: yellow }
10+
:not(pre).r { background: orange }
11+
:not(pre).fo { background: red }
12+
.open { border: solid red; }
13+
:target { box-shadow: 0.25em 0.25em 0.25em; }
14+
a[href^=mid], a[href~=flatten] { text-decoration: none; }
15+
abbr { font-weight: bold; }
16+
</style>
17+
18+
<h1>CSS Scroll Snapping Level 1 Disposition of Comments for 2016-10-20 CR</h1>
19+
20+
<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>
21+
22+
<p>Editor's Draft: <a href="http://drafts.csswg.org/css-scroll-snap-1/">http://drafts.csswg.org/css-scroll-snap-1/</a>
23+
24+
<p>The following color coding convention is used for comments:</p>
25+
26+
<ul>
27+
<li class="a">Accepted or Rejected and positive response
28+
<li class="r">Rejected and no response
29+
<li class="fo">Rejected and negative response
30+
<li class="d">Deferred
31+
<li class="oi">Out-of-Scope or Invalid and not verified
32+
</ul>
33+
34+
<p class=open>Open issues are marked like this</p>
35+
36+
<p>An issue can be closed as <code>Accepted</code>, <code>OutOfScope</code>,
37+
<code>Invalid</code>, <code>Rejected</code>, or <code>Retracted</code>.
38+
<code>Verified</code> indicates commentor's acceptance of the response.</p>
39+
<pre class=' a' id='issue-1'>
40+
<span>Issue 1. <a href='#issue-1'>#</a></span>
41+
<span>Summary: Examples and syntax of scroll-snap-type conflict</span>
42+
<span>From: Wenson Hsieh</span>
43+
<span>Comment: <a href='https://github.com/w3c/csswg-drafts/issues/827'>https://github.com/w3c/csswg-drafts/issues/827</a></span>
44+
<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>
45+
<span>Changes: <a href='https://github.com/w3c/csswg-drafts/commit/7a20d00238aac3ddbdd8d5dd7e74ff81dd29ba76'>https://github.com/w3c/csswg-drafts/commit/7a20d00238aac3ddbdd8d5dd7e74ff81dd29ba76</a></span>
46+
<span class="a">Closed: Accepted</span>
47+
<span>Resolved: Editorial</span></pre>
48+
<pre class=' a' id='issue-2'>
49+
<span>Issue 2. <a href='#issue-2'>#</a></span>
50+
<span>Summary: Clarify that css-scroll-snap doesn't dictate any particular input method</span>
51+
<span>From: Benoit Girard</span>
52+
<span>Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1305'>https://github.com/w3c/csswg-drafts/issues/1305</a></span>
53+
<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>
54+
<span>Changes: <a href='https://github.com/w3c/csswg-drafts/commit/9760282d421c772b0e08b745149b8f7d21208ff1'>https://github.com/w3c/csswg-drafts/commit/9760282d421c772b0e08b745149b8f7d21208ff1</a></span>
55+
<span class="a">Closed: Accepted</span>
56+
<span>Resolved: Editorial</span>
57+
<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>
58+
<pre class=' oi' id='issue-3'>
59+
<span>Issue 3. <a href='#issue-3'>#</a></span>
60+
<span>Summary: Specify how scroll-padding expands out</span>
61+
<span>From: Peter Linss</span>
62+
<span>Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1050'>https://github.com/w3c/csswg-drafts/issues/1050</a></span>
63+
<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>
64+
<span class="oi">Closed: Invalid</span></pre>
65+
<pre class=' a' id='issue-4'>
66+
<span>Issue 4. <a href='#issue-4'>#</a></span>
67+
<span>Summary: Should negative scroll-padding be allowed</span>
68+
<span>From: fantasai</span>
69+
<span>Comment: <a href='https://github.com/w3c/csswg-drafts/issues/1084'>https://github.com/w3c/csswg-drafts/issues/1084</a></span>
70+
<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>
71+
<span>Changes: <a href='https://github.com/w3c/csswg-drafts/commit/8158a651b75e81db6dcbdffd17c91e3edb81de5d'>https://github.com/w3c/csswg-drafts/commit/8158a651b75e81db6dcbdffd17c91e3edb81de5d</a></span>
72+
<span class="a">Closed: Accepted</span>
73+
<span>Resolved: CSSWG Telecon 2017-05-17</span>
74+
<span class="a">Verified: Reporter is editor</span></pre>
75+
<pre class=' a' id='issue-5'>
76+
<span>Issue 5. <a href='#issue-5'>#</a></span>
77+
<span>Summary: Clarify how visibility requirement makes snap x/y snap positions interdependent</span>
78+
<span>From: Majid Valipour</span>
79+
<span>Comment: <a href='https://github.com/w3c/csswg-drafts/issues/950'>https://github.com/w3c/csswg-drafts/issues/950</a></span>
80+
<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>
81+
<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>
82+
<span class="a">Closed: Accepted</span>
83+
<span>Resolved: Editorial</span></pre>
84+
<script>
85+
(function () {
86+
var sheet = document.styleSheets[0];
87+
function addCheckbox(className) {
88+
var element = document.querySelector('*.' + className);
89+
var span = document.createElement('span');
90+
span.innerHTML = element.innerHTML;
91+
element.innerHTML = null;
92+
var check = document.createElement('input');
93+
check.type = 'checkbox';
94+
if (className == 'open') {
95+
check.checked = false;
96+
sheet.insertRule('pre:not(.open)' + '{}', sheet.cssRules.length);
97+
check.onchange = function (e) {
98+
rule.style.display = this.checked ? 'none' : 'block';
99+
}
100+
}
101+
else {
102+
check.checked = true;
103+
sheet.insertRule('pre.' + className + '{}', sheet.cssRules.length);
104+
check.onchange = function (e) {
105+
rule.style.display = this.checked ? 'block' : 'none';
106+
}
107+
}
108+
var rule = sheet.cssRules[sheet.cssRules.length - 1];
109+
element.appendChild(check);
110+
element.appendChild(span);
111+
}
112+
['a', 'd', 'fo', 'oi', 'r', 'open'].forEach(addCheckbox);
113+
}());
114+
</script>

0 commit comments

Comments
 (0)