Skip to content

Commit 332b95a

Browse files
committed
[css-snappoints] Changing 'snap points' to 'snap positions' for consistency; snap positions is defined but snap points is not. Leaving shortname/url/title/issue tracking for now so I don't mess anything up but they should change too.
1 parent 82527a2 commit 332b95a

3 files changed

Lines changed: 12 additions & 12 deletions

File tree

css-snappoints/Overview.src.html

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -10,9 +10,9 @@ <h1>CSS Scroll Snap Points Module Level 1</h1>
1010
ED: http://dev.w3.org/csswg/css-snappoints/
1111
Editor: Matt Rakow, Microsoft
1212
Editor: Jacob Rossi, Microsoft
13-
Abstract: This module contains features to control panning and scrolling behavior with "snap points".
13+
Abstract: This module contains features to control panning and scrolling behavior with "snap positions".
1414
!Issue Tracking: <a href="http://wiki.csswg.org/spec/css-snappoints">http://wiki.csswg.org/spec/css-snappoints</a>
15-
Ignored Terms: scroll-snap-points-*, containing block chain
15+
Ignored Terms: scroll-snap-positions-*, containing block chain
1616
</pre>
1717

1818
<h2 id="intro">Introduction</h2>
@@ -35,7 +35,7 @@ <h2 id="intro">Introduction</h2>
3535
For instance, it is easy for a user to land at an awkward scroll offset
3636
which leaves a page partially on-screen when panning.
3737

38-
To this end, we introduce scroll snap points
38+
To this end, we introduce scroll snap positions
3939
which enforce the scroll offsets that a <a>scroll container's</a> visual viewport may end at
4040
after a scrolling operation has completed.
4141

@@ -62,7 +62,7 @@ <h2 id="examples">Motivating Examples</h2>
6262
are used to build a photo gallery. In this example the <a>scroll container</a>
6363
is larger than the photos contained within (such that multiple images may be seen simultaneously), and the image
6464
sizes vary. Using mandatory element-based snap
65-
points, scrolling will always complete with an image centered in the <a>scroll container's</a> visual viewport.
65+
positions, scrolling will always complete with an image centered in the <a>scroll container's</a> visual viewport.
6666

6767
<pre>
6868
img {
@@ -77,7 +77,7 @@ <h2 id="examples">Motivating Examples</h2>
7777
overflow-y: hidden;
7878
white-space: nowrap;
7979
/* Requires that the scroll offset always be
80-
at a valid snap point when the scrolling
80+
at a valid snap position when the scrolling
8181
operation completes. */
8282
scroll-snap-type: mandatory;
8383
}
@@ -94,7 +94,7 @@ <h2 id="examples">Motivating Examples</h2>
9494
</pre>
9595

9696
<figure>
97-
<img src="element_snap_points.png" alt="">
97+
<img src="element_snap_positions.png" alt="">
9898

9999
<figcaption>
100100
The layout of the scroll container's contents in the example.
@@ -109,8 +109,8 @@ <h2 id="examples">Motivating Examples</h2>
109109
<div class="example">
110110
This example builds a paginated document that aligns each page near to (but not exactly on) the edge of the <a>scroll container</a>.
111111
This allows the previous page to "peek" in from above in order to make the user aware that they are not yet at the top of the document.
112-
Using proximity snap points instead of mandatory snap points allows the user to stop halfway through a page (rather than forcing them
113-
to snap one page at a time). However, if a scrolling operation would finish near a snap point, then the scroll will be adjusted to
112+
Using proximity snap positions instead of mandatory snap positions allows the user to stop halfway through a page (rather than forcing them
113+
to snap one page at a time). However, if a scrolling operation would finish near a snap position, then the scroll will be adjusted to
114114
align the page as specified.
115115

116116
<pre>
@@ -126,8 +126,8 @@ <h2 id="examples">Motivating Examples</h2>
126126
/* Specifies that each element's snap area should
127127
align with a 100px offset from the top edge. */
128128
scroll-snap-padding: 100px 0 0;
129-
/* Encourages scrolling to end at a snap point when the
130-
operation completes, if it is near a snap point */
129+
/* Encourages scrolling to end at a snap position when the
130+
operation completes, if it is near a valid snap position */
131131
scroll-snap-type: proximity;
132132
}
133133
</pre>
@@ -142,7 +142,7 @@ <h2 id="examples">Motivating Examples</h2>
142142
</pre>
143143

144144
<figure>
145-
<img src="element_snap_points_offset.png" alt="">
145+
<img src="element_snap_positions_offset.png" alt="">
146146

147147
<figcaption>
148148
The layout of the scroll container's contents in the example.
@@ -200,7 +200,7 @@ <h2 id="definitions">Definitions</h2>
200200

201201
<h2 id="scroll-snap-type">Scroll Snap Types: the 'scroll-snap-type' property</h2>
202202

203-
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 points; this is left up to the user agent.
203+
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 position; this is left up to the user agent.
204204

205205
<p class="issue">
206206
<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.
File renamed without changes.

0 commit comments

Comments
 (0)