Merge branch 'master' into improve-distance-function

Author: Jihye Hong

css-conditional-3/Overview.bs

@@ -19,7 +19,6 @@ Abstract: This module contains the features of CSS for conditional processing of
   conditional processing.
 At Risk: The inclusion of @font-face rules and @keyframes rules as allowed within all of the @-rules in this specification is at risk, though only because of the relative rates of advancement of specifications.  If this specification is able to advance faster than one or both of the specifications defining those rules, then the inclusion of those rules will move from this specification to the specification defining those rules.
 At Risk: The addition of support for @-rules inside of conditional grouping rules is at risk; if interoperable implementations are not found, it may be removed to advance the other features in this specification to Proposed Recommendation.
-At Risk: The @supports rule is at risk; if interoperable implementations are not found, it may be removed to advance the other features in this specification to Proposed Recommendation.
 Default Highlight: css
 </pre>
 

css-exclusions-1/Overview.bs

@@ -856,3 +856,25 @@ Acknowledgments</h2>
   Eugene Veselov,
   Stephen Zilles
   and the CSS Working Group members.
+
+<h2 class="no-num" id="changes">Changes</h2>
+
+  <h3 class="no-num" id="recent-changes">
+  Changes from the <a href="https://www.w3.org/TR/2015/WD-css3-exclusions-20150115/">15 January 2015 Working Draft</a></h3>
+
+  <h3 class="no-num" id="changes-2013">
+  Changes from the <a href="https://www.w3.org/TR/2013/WD-css3-exclusions-20130528/">28 May 2013 Working Draft</a></h3>
+
+  <ul>
+    <li>Editorial fixes.
+  </ul>
+
+  <h3 class="no-num" id="changes-2012">
+  Changes from the <a href="https://www.w3.org/TR/2012/WD-css3-exclusions-20120503/">3 May 2012 Working Draft</a></h3>
+
+  <ul>
+    <li>Split Exclusions from Shapes.
+    <li>Improved exclusion order example.
+    <li>Editorial and markup fixes.
+    <li>See also the Changes section of <a href="https://www.w3.org/TR/css-shapes/#20120503">CSS Shapes</a>.
+  </ul>

css-font-loading-3/Overview.bs

@@ -990,20 +990,18 @@ Interaction with CSS Font Loading and Matching</h3>
 -->
 
 <h2 id='font-face-source'>
-The <code>FontFaceSource</code> interface</h2>
+The <code>FontFaceSource</code> mixin</h2>
 
 	<pre class='idl'>
-		[Exposed=(Window,Worker),
-		 NoInterfaceObject]
-		interface FontFaceSource {
+		interface mixin FontFaceSource {
 			readonly attribute FontFaceSet fonts;
 		};
 
-		Document implements FontFaceSource;
-		WorkerGlobalScope implements FontFaceSource;
+		Document includes FontFaceSource;
+		WorkerGlobalScope includes FontFaceSource;
 	</pre>
 
-	Any document, workers, or other context which can use fonts in some manner must implement the {{FontFaceSource}} interface.
+	Any document, workers, or other context which can use fonts in some manner must include the {{FontFaceSource}} mixin.
 	The value of the context’s {{fonts}} attribute is its <dfn>font source</dfn>,
 	which provides all of the fonts used in font-related operations,
 	unless defined otherwise.

css-gcpm-3/Overview.bs

@@ -896,7 +896,15 @@ h6 { bookmark-level: 6 }
 
 <h2 class="no-num" id="changes">Appendix C: Changes</h2>
 
-  Changes since the <a href="https://hg.csswg.org/drafts/raw-file/6a5c44d11c2b/css-gcpm/Overview.html">24 September 2013 Editor’s Draft</a> are:
+Changes since the <a href="http://www.w3.org/TR/2014/WD-css-gcpm-3-20140513/">13 May 2014 Working Draft</a>:
+
+<ul>
+	<li>Clarify that bookmark is only created via 'bookmark-level' property. Remove <css>none</css> value from 'bookmark-label'.</li>
+	<li>Move the cross references, leaders, and bookmarks sections to the <a href="https://www.w3.org/TR/css-content-3/">CSS Generated Content Module</a>.</li>
+</ul>
+
+
+  Changes since the <a href="https://hg.csswg.org/drafts/raw-file/6a5c44d11c2b/css-gcpm/Overview.html">24 September 2013 Editor’s Draft</a>:
 
 
 <ul>
@@ -913,7 +921,8 @@ h6 { bookmark-level: 6 }
 
 
 </ul>
-In addition to the above changes, many other changes have been made since the <a href="https://www.w3.org/TR/2011/WD-css3-gcpm-20111129/">29 November 2011 Working Draft</a>:
+
+Changes since the <a href="https://www.w3.org/TR/2011/WD-css3-gcpm-20111129/">29 November 2011 Working Draft</a>:
 
 <ul>
 <li>

css-line-grid-1/Overview.bs

@@ -757,6 +757,8 @@ Since <a href="https://www.w3.org/TR/2014/WD-css-line-grid-1-20140916/">Septembe
 		<li>Added flex and grid container applicability for line-grid</li>
 		<li>Added normative text for line-snap examples</li>
 		<li>Added @page and root element line grid handling</li>
+		<li>Made the dependency on line-height-step explicit</li>
+		<li>''match-parent'' creates new line grid for orthoganal flows</li>
 	</ul>
 
 <h3 class="no-num" id="20140403">

css-lists-3/Overview.bs

@@ -1435,8 +1435,15 @@ Acknowledgments</h2>
 	Simon Montagu (Mozilla, smontagu@smontagu.org)
 
 
-<h2 class="no-num" id="changes">
-Changes From CSS2.1</h2>
+<h2 class="no-num" id="changes">Changes</h2>
+
+This section documents the changes since previous publications.
+
+<h3 id="changes-20140320">Changes since the 20 March 2014 WD</h3>
+
+Use <<custom-ident>> consistently for counter names.
+
+<h3>Changes From CSS2.1</h3>
 
 	<p>As described in the introduction section, there are significant changes in this module when
 	compared to CSS2.1.

css-multicol-1/Overview.bs

@@ -25,7 +25,7 @@ Link Defaults: css-color (property) color, css2 (property) max-height, css-backg
 At Risk: column-gap accepting <<length-percentage>> instead of <<length>>
 </pre>
 <pre class="link-defaults">
-spec:css22; type:dfn; text: table wrapper box
+spec:css-sizing-3; type:property; text:min-height
 </pre>
 
 <style type="text/css">
@@ -51,13 +51,9 @@ Introduction</h2>
 	that the content of an element is to be laid out in multiple
 	columns.
 
-	On the Web, tables have also been used to describe multi-column
-	layouts. The main benefit of using CSS-based columns is flexibility;
-	content can flow from one column to another, and the number of columns
-	can vary depending on the size of the viewport. Removing presentation
-	table markup from documents allows them to more easily be presented on
-	various output devices including speech synthesizers and small mobile
-	devices.
+	Other layout methods in CSS, when applied to a parent element, change the display properties of the direct children. For example if a three column grid layout is created, the direct children of the grid container become grid items and are placed into the column tracks, one element per cell with additional rows created as needed.
+
+	The child elements of a multi-column container however continue in normal flow, that flow is arranged into a number of columns. These columns have a flexible inline size, and therefore respond to available space by changing the size or number of columns displayed. 
 
 	Multi-column layouts are easy to describe in CSS. Here is a simple example:
 
@@ -586,7 +582,7 @@ Two assumptions are being made by the pseudo-algorithm:
 	(11)  W := max(0, ((U + column-gap)/N - column-gap))
 	</pre>
 
-	For the purpose of finding the number of auto-repeated tracks, the UA must floor the track size to a UA-specified value to avoid division by zero. It is suggested that this floor be 1px or less.
+	For the purpose of finding the number of auto-repeated columns, the UA must floor the column size to a UA-specified value to avoid division by zero. It is suggested that this floor be 1px or less.
 
 	In fragmented contexts such as in paged media, user agents may perform this calculation on a
 	per-fragment basis.
@@ -1147,25 +1143,21 @@ Filling columns</h2>
 			<wpt>
 			multicol-fill-auto-001.xht
 			multicol-fill-auto-002.xht
-			multicol-fill-auto-003.xht
 			multicol-fill-auto-block-children-001.xht
 			multicol-fill-auto-block-children-002.xht
 			multicol-fill-balance-001.xht
 			</wpt>
 	</dl>
 
-	<!--
 	In continuous contexts, this property will only be consulted if the
-	length of columns has been constrained. Otherwise, columns will
+	length of columns has been constrained in the block dimension, including min and max constraints (e.g., 'height', 'min-height', 'max-height'). Otherwise, columns will
 	automatically be balanced.
-	-->
 
-	In continuous contexts, this property does not have any effect when there are overflow columns.
+	<wpt>
+	multicol-fill-auto-003.xht
+	</wpt>
 
-	<!--
-	In fragmented contexts, this property will only have
-	effect on the last fragment the multicol container appears in.
-	-->
+	In continuous contexts, this property does not have any effect when there are overflow columns.
 
 	<div class="example">
 		In this example, an article only has one short paragraph which fits
@@ -1189,12 +1181,12 @@ Filling columns</h2>
 	</div>
 
 	<div class="example">
-		In this example, column balancing is turned off:
+		In this example, column balancing is turned off, and the article has a height:
 
 		<pre highlight="css">
 		article {
 			width: 60em;
-			height: auto;
+			height: 4em;
 			columns: 4;
 			column-fill: auto;
 		}
@@ -1416,8 +1408,15 @@ Pagination and overflow outside multicol containers</h3>
 
 This appendix is <em>informative</em>.
 
-<h3 id="changes-from-20171005">Changes from the <a href="https://www.w3.org/TR/2017/WD-css-multicol-1-20171005/">Working Draft (WD) of 5 October 2017</a></h3>
+<h3 id="changes-from-20180528">Changes from the <a href="https://www.w3.org/TR/2018/WD-css-multicol-1-20180528/">Working Draft (WD) of 28 May 2018</a></h3>
 <ul>
+	<li>Added the paragraph "In continuous contexts, this property will only be consulted if the length of columns has been constrained in the block dimension, including min and max constraints (e.g., 'height', 'min-height', 'max-height'). Otherwise, columns will automatically be balanced." This paragraph (without the additional detail regarding min and max constraints) was commented out in 2012, causing an interoperability issue. Also corrected the example of content ending up all in the first column, by adding the height constraint. Resolved <a href="https://github.com/w3c/csswg-drafts/issues/3224#issuecomment-468089503">28 February 2019</a></li>
+	<li>Updated the introduction to remove mention of the benefits of multicol over using tables for layout and instead refer to the unique characteristics of multicol. Editorial change referenced in <a href="https://github.com/w3c/csswg-drafts/issues/3654">issue 3654</a>.</li>
+	<li>Changed the sentence added in the pseudo-algorithm section after the 7 Jan 2016 resolution, to refer to <em>columns</em> and not <em>tracks</em> as tracks are not defined in this specification. Resolved <a href="https://github.com/w3c/csswg-drafts/issues/3649#issuecomment-472505520">13 March 2019</a>.</li>
+	<li>Changes and clarifications to the SVG images used in the specification.</li>
+</ul>
+
+<h3 id="changes-from-20171005">Changes from the <a href="https://www.w3.org/TR/2017/WD-css-multicol-1-20171005/">Working Draft (WD) of 5 October 2017</a></h3>
 	<li>Changed references to paged media to refer to fragmented contexts. Resolved <a href="https://github.com/w3c/csswg-drafts/issues/1746#issuecomment-380731574">12 Apr 2018</a>.</li>
 	<li>Changed a line regarding the <code>column-fill</code> property:
 	<br><q>In continuous media, this property does not have any effect in