[css-display] Add changes section

Author: fantasai

css-display/Overview.bs

@@ -417,6 +417,8 @@ Controlling box generation: the 'box-suppress' property</h2>
 			must work as normal on this element and its descendants.
 	</dl>
 
+	Issue: We welcome better naming suggestions on this property.
+
 <h2 id='run-in'>
 Run-In Layout</h2>
 
@@ -493,6 +495,8 @@ Run-In Layout</h2>
 	Issue: Should out-of-flow elements get reparented, left behind, or break apart the sequence?
 	<a href="http://lists.w3.org/Archives/Public/www-style/2012Aug/0257.html">See thread.</a>
 
+	Note: This run-in model is slightly different from the one proposed in earlier revisions of [[!CSS21]].
+
 <h2 id='glossary'>
 Glossary</h2>
 
@@ -577,3 +581,18 @@ Acknowledgments</h2>
 	We would also like to thank the many JavaScript libraries such as jQuery
 	which have hacked around the "what 'display' should I give it when you call .show()?" problem,
 	making it extremely clear that something needed to be done on our part.
+
+<h2 class=no-num id="changes">
+Changes</h2>
+
+	Changes since the <a href="http://www.w3.org/TR/2014/WD-css-display-3-20140220/">20 Feburary 2014 Working Draft</a> include:
+
+	<ul>
+		<li>Renamed <css>display-box</css> to 'box-suppress' and <css>display-extras</css> to 'display-list'.
+		<li>Moved the ''display-outside/contents'' value from 'box-suppress' to 'display-outside'.
+		<li>Added ''hide'' value to 'box-suppress'.
+		<li>Added <a>blockification</a> and <a>inlinification</a> rules.
+		<li>Added ''display: run-in'' and defined its layout in [[#run-in]].
+		<li>Various editorial improvements.
+		<li>Added [[#glossary]], incorporating key CSS2.1 terms.
+	</ul>

css-display/Overview.html

@@ -128,6 +128,7 @@ <h2 class="no-num no-toc no-ref heading settled" id=contents><span class=content
 	<li><a href=#run-in><span class=secno>4</span>  Run-In Layout</a>
 	<li><a href=#glossary><span class=secno>5</span>  Glossary</a>
 	<li><a href=#acknowledgments><span class=secno></span>  Acknowledgments</a>
+	<li><a href=#changes><span class=secno></span>  Changes</a>
 	<li><a href=#conformance><span class=secno></span>  Conformance</a>
 		<ul class=toc>
 		<li><a href=#conventions><span class=secno></span>  Document conventions</a>
@@ -506,6 +507,8 @@ <h2 class="heading settled" data-level=3 id=box-suppress><span class=secno>3 </s
 			must work as normal on this element and its descendants.</p>
 	</dl>
 
+<p class=issue id=issue-f3da3890><a class=self-link href=#issue-f3da3890></a>We welcome better naming suggestions on this property.</p>
+
 <h2 class="heading settled" data-level=4 id=run-in><span class=secno>4 </span><span class=content>
 Run-In Layout</span><a class=self-link href=#run-in></a></h2>
 
@@ -579,6 +582,8 @@ <h2 class="heading settled" data-level=4 id=run-in><span class=secno>4 </span><s
 <p class=issue id=issue-0c2c54c6><a class=self-link href=#issue-0c2c54c6></a>Should out-of-flow elements get reparented, left behind, or break apart the sequence?
 	<a href=http://lists.w3.org/Archives/Public/www-style/2012Aug/0257.html>See thread.</a></p>
 
+<p class=note>Note: This run-in model is slightly different from the one proposed in earlier revisions of <a data-biblio-type=normative data-link-type=biblio href=#biblio-css21 title=biblio-CSS21>[CSS21]</a>.</p>
+
 <h2 class="heading settled" data-level=5 id=glossary><span class=secno>5 </span><span class=content>
 Glossary</span><a class=self-link href=#glossary></a></h2>
 
@@ -664,6 +669,23 @@ <h2 class="no-num heading settled" id=acknowledgments><span class=content>
 	which have hacked around the "what <a class=property data-link-type=propdesc href=#propdef-display title=display>display</a> should I give it when you call .show()?" problem,
 	making it extremely clear that something needed to be done on our part.</p>
 
+<h2 class="no-num heading settled" id=changes><span class=content>
+Changes</span><a class=self-link href=#changes></a></h2>
+
+<p>Changes since the <a href=http://www.w3.org/TR/2014/WD-css-display-3-20140220/>20 Feburary 2014 Working Draft</a> include:</p>
+
+	<ul>
+		<li>Renamed <span class=css>display-box</span> to <a class=property data-link-type=propdesc href=#propdef-box-suppress title=box-suppress>box-suppress</a> and <span class=css>display-extras</span> to <a class=property data-link-type=propdesc href=#propdef-display-list title=display-list>display-list</a>.
+		<li>Moved the <a class=css data-link-for=display-outside data-link-type=maybe href=#valdef-display-outside-contents title=contents>contents</a> value from <a class=property data-link-type=propdesc href=#propdef-box-suppress title=box-suppress>box-suppress</a> to <a class=property data-link-type=propdesc href=#propdef-display-outside title=display-outside>display-outside</a>.
+		<li>Added <a class=css data-link-type=maybe href=#valdef-box-suppress-hide title=hide>hide</a> value to <a class=property data-link-type=propdesc href=#propdef-box-suppress title=box-suppress>box-suppress</a>.
+		<li>Added <a data-link-type=dfn href=#blockify title=blockification>blockification</a> and <a data-link-type=dfn href=#inlinify title=inlinification>inlinification</a> rules.
+		<li>Added <a class=css data-link-type=propdesc href=#propdef-display title=display>display: run-in</a> and defined its layout in <a data-section="" href=#run-in>§4 
+Run-In Layout</a>.
+		<li>Various editorial improvements.
+		<li>Added <a data-section="" href=#glossary>§5 
+Glossary</a>, incorporating key CSS2.1 terms.
+	</ul>
+
 <h2 class="no-ref no-num heading settled" id=conformance><span class=content>
 Conformance</span><a class=self-link href=#conformance></a></h2>
 
@@ -905,5 +927,5 @@ <h2 class="no-num no-ref heading settled" id=property-index><span class=content>
 
 <h2 class="no-num heading settled" id=issues-index><span class=content>Issues Index</span><a class=self-link href=#issues-index></a></h2><div style="counter-reset: issue"><div class=issue><a class=css data-link-for=display-outside data-link-type=maybe href=#valdef-display-outside-contents title=contents>contents</a> currently only has an effect on box generation and layout.
 			Other things that care about the document tree are unaffected, like counter scopes.
-			Is this what we want?<a href=#issue-1cacf007> ↵ </a></div><div class=issue>Should out-of-flow elements get reparented, left behind, or break apart the sequence?
+			Is this what we want?<a href=#issue-1cacf007> ↵ </a></div><div class=issue>We welcome better naming suggestions on this property.<a href=#issue-f3da3890> ↵ </a></div><div class=issue>Should out-of-flow elements get reparented, left behind, or break apart the sequence?
 	<a href=http://lists.w3.org/Archives/Public/www-style/2012Aug/0257.html>See thread.</a><a href=#issue-0c2c54c6> ↵ </a></div><div class=issue>wordsmith this.<a href=#issue-3b09a388> ↵ </a></div></div>