Skip to content

Commit 2a1c4c5

Browse files
committed
[css-scroll-snap] Finish fixing wrapping. (No content changes, just white space.)
1 parent d1d623f commit 2a1c4c5

1 file changed

Lines changed: 17 additions & 2 deletions

File tree

css-scroll-snap/Overview.bs

Lines changed: 17 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -275,13 +275,28 @@ Scroll Snapping Rules: the 'scroll-snap-type' property {#scroll-snap-type}
275275
<dd>
276276
If specified on a <a>scroll container</a>, the <a>scroll container</a> is required to be <a>snapped</a> to a snap position when there are no active scrolling operations. If a reachable snap position exists then the scroll container must <a>snap</a> at the termination of a scroll (if none exist then no <a>snapping</a> occurs).
277277

278-
If the content changes such that the scroll container would no longer be <a>snapped</a> (e.g. content is added, moved, deleted, resized) to the same snap position it was snapped to before the content change, the scroll container must be re-snapped. If the same snap position it was snapped to before the content change still exists (e.g. its associated element was not deleted) and is reachable, the scroll container must be re-snapped to that same snap position after the content change.
278+
If the content changes
279+
such that the scroll container would no longer be <a>snapped</a>
280+
(e.g. content is added, moved, deleted, resized)
281+
to the same snap position it was snapped to before the content change,
282+
the scroll container must be re-snapped.
283+
If the same snap position it was snapped to before the content change
284+
still exists (e.g. its associated element was not deleted) and is reachable,
285+
the scroll container must be re-snapped to that same snap position
286+
after the content change.
279287

280288
<dt><dfn>proximity</dfn>
281289
<dd>
282290
If specified on a <a>scroll container</a>, the <a>scroll container</a> may <a>snap</a> to a snap position at the termination of a scroll, at the discretion of the UA given the parameters of the scroll.
283291

284-
If the content changes such that the scroll container would no longer be <a>snapped</a> (e.g. content is added, moved, deleted, resized) to the same snap position it was snapped to before the content change and that same snap position still exists (e.g. its associated element was not deleted) and is reachable, the scroll container must be re-snapped to that same snap position after the content change.
292+
If the content changes
293+
such that the scroll container would no longer be <a>snapped</a>
294+
(e.g. content is added, moved, deleted, resized)
295+
to the same snap position it was snapped to before the content change
296+
and that same snap position still exists
297+
(e.g. its associated element was not deleted) and is reachable,
298+
the scroll container must be re-snapped to that same snap position
299+
after the content change.
285300

286301
Issue: The text for mandatory and proximity resnapping requirements has some overlap -- try to rewrite this more concisely and without repetition without altering functionality
287302
</dl>

0 commit comments

Comments
 (0)