Skip to content

Commit 259f885

Browse files
committed
[css-scroll-snap] More fixes to diff.
1 parent 620a495 commit 259f885

2 files changed

Lines changed: 87 additions & 75 deletions

File tree

css-scroll-snap/diff-notes.html

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -37,8 +37,6 @@ <h1>CSS Scroll Snap Diff Annotations</h1>
3737
* Run <code> generation
3838
-->
3939

40-
<p>Issue: Decide between “scroll position” and “scroll offset” as both are used randomly interchangeably.
41-
4240
<p>This is a list of <a href="diff">differences</a>
4341
between the <a href="http://www.w3.org/TR/css-snappoints-1/">CSS Scroll Snap Module</a> as maintained by Matt Rakow
4442
and the <a href="http://drafts.csswg.org/css-scroll-snap/">CSS Scroll Snap Module Change Proposal</a> maintained by Tab and fantasai.
@@ -340,6 +338,7 @@ <h2>Specific Changes</h2>
340338
<blockquote>
341339
<p>If the content <ins>or layout of the scroll container</ins> changes e.g. content is added, moved, deleted, resized), the UA must re-evaluate, and potentially re-snap if necessary, the resulting scroll offset once the positions of the content have restabilized. <ins>This can result in no snapping, (e.g. if there are no nearby snap positions for a proximitiy-snapping scroll container).</ins> However, if there was a previously-snapped snap position (associated with the same element) that still exists after such changes, the UA must remain snapped to it<ins>—even if the changes would have placed a different snap position closer to the current scroll offset</ins>. Otherwise, the scroll container must be re-snapped as if the user had scrolled to its current scroll offset (as an explicit scroll, if no other scroll operation is active).
342340
</blockquote>
341+
</ul>
343342

344343
<dt id=change-relxy>Clarification: Corresponding Dimensions
345344
<dd>
@@ -470,10 +469,12 @@ <h3 class="heading settled" data-level="7.2" id="snap-dimensions"><span class="s
470469
as in <a href="http://labs.jensimmons.com/examples/image-gallery-flexbox-1.html">this example</a> (Flexbox)
471470
or <a href="http://labs.jensimmons.com/examples/image-gallery-grid-1.html">this one</a> (Grid).
472471
Again, we're happy to leave this to level 2, but do want the feature design published for future reference)
473-
472+
<!--
474473
<dt id=change-valid>Valid snap positions
475474
<dd>
476475
We make a distinction between snap positions in general and valid snap positions.
476+
I can't remember why.
477+
-->
477478

478479
<dt id=change-subheads>Descriptive Subheadings
479480
<dd>
@@ -654,15 +655,15 @@ <h3 class="heading settled" data-level="7.2" id="snap-dimensions"><span class="s
654655
<blockquote>
655656
the scroll container may snap to a valid snap position at the termination of a scroll<ins>,</ins> at the discretion of the UA given the parameters of the scroll.
656657
</blockquote>
657-
<li>This addition clarifies the nature of relevant changes:
658-
<blockquote>
659-
If the content <ins>or layout of the scroll container</ins> changes (e.g. content is added, moved, deleted, resized),
660-
</blockquote>
661-
<li>This addition
662658
</ul>
663659
</dd>
664660
<dt id="change-ack">Acknowledgements Update
665661
<dd>
666662
We've added a list of the people who have contributed the spec,
667663
and noted that their proposals were mostly accepted rather than mostly ignored.
668664
</dl>
665+
666+
<blockquote cite="https://lists.w3.org/Archives/Public/www-style/2014Jan/0591.html">
667+
<p>Anyway, here is some feedback about the new draft. I hope it's not ignored again.
668+
<address>Robert O'Callahan, www-style, 30 January 2014</address>
669+
</blockquote>

0 commit comments

Comments
 (0)