[css-scroll-snap] Add diffs and issue links to changes list.

Author: fantasai

css-scroll-snap-1/Overview.bs

@@ -520,7 +520,8 @@ Scroll Snapping Area: the 'scroll-margin' property {#scroll-margin}
     or the target of {{scrollIntoView()}}),
     the UA should use the element's <a>scroll snap area</a>,
     rather than just its border box,
-    to determine which area of the <a>scrollable overflow region</a> to bring into view.
+    to determine which area of the <a>scrollable overflow region</a>
+    to bring into view.
 
 <!--
    ███    ██       ████  ██████   ██    ██
@@ -1095,15 +1096,46 @@ Changes {#changes}
 Changes Since 24 August 2017 CR {#changes-20170824}
 ---------------------------------------------------
 
-    Changes since the <a href="https://www.w3.org/TR/2017/CR-css-scroll-snap-1-20170824/">24 August 2017 Candidate Recommendation</a> include:
+	Changes since the <a href="https://www.w3.org/TR/2017/CR-css-scroll-snap-1-20170824/">24 August 2017 Candidate Recommendation</a> include:
 
-	* '':target''/{{scrollIntoView()}}/etc should take 'scroll-margin' into account,
-		regardless of whether snapping is turned on or not.
-	* '':target''/{{scrollIntoView()}}/etc must (rather than should)
-		use snap positions if snapping is turned on.
-	* Renamed <css>scroll-snap-margin</css> to 'scroll-margin'
-		to reflect its more generic role in providing breathing space
-		for scrolling to an element regardless of snapping behavior.
+	<ul>
+		<li id="change-2017-scroll-margin">
+			'':target''/{{scrollIntoView()}}/etc should take 'scroll-margin' into account,
+			regardless of whether snapping is turned on or not.
+			(<a href="https://drafts.csswg.org/css-scroll-snap-1/issues-cr-2016-08#issue-1">Issue 1</a>
+			<blockquote>
+				<p><ins>If a page is navigated to a fragment that defines a target element
+				(one that would be matched by '':target'',
+				or the target of {{scrollIntoView()}}),
+				the UA should use the element's <a>scroll snap area</a>,
+				rather than just its border box,
+				to determine which area of the <a>scrollable overflow region</a>
+				to bring into view.</ins></p>
+			</blockquote>
+
+		<li id="change-2017-target-snap-must">
+			'':target''/{{scrollIntoView()}}/etc must (rather than should)
+			use snap positions if snapping is turned on.
+			(<a href="https://drafts.csswg.org/css-scroll-snap-1/issues-cr-2016-08#issue-1">Issue 1</a>
+			<blockquote>
+				<p>If a page is navigated to a fragment that defines a target element
+				(one that would be matched by '':target'',
+				or the target of {{Element/scrollIntoView()}}),
+				and that element defines some <a>snap positions</a>,
+				the user agent <del>should</del> <ins>must</ins> <a>snap</a>
+				to one of that element’s <a>snap positions</a>
+				<ins>if its nearest <a>scroll container</a> is a <a>scroll snap container</a></ins>.
+				The user agent <em>may</em> also do this even when
+				the <a>scroll container</a> has ''scroll-snap-type: none''.</p>
+			</blockquote>
+
+		<li id="change-2017-rename-scroll-margin">
+			Renamed <css>scroll-snap-margin</css> to 'scroll-margin'
+			to reflect its more generic role in providing breathing space
+			for scrolling to an element regardless of snapping behavior.
+			(<a href="https://drafts.csswg.org/css-scroll-snap-1/issues-cr-2016-08#issue-4">Issue 4</a>)
+
+	A <a href="https://drafts.csswg.org/css-scroll-snap-1/issues-cr-2016-08">Disposition of Comments</a> is available.
 
 Changes Since 20 October 2016 CR {#changes-20161020}
 ----------------------------------------------------