[css-contain] Terminology clean up: **establish** a formatting context

Closes w3c#1457

Author: frivoal

css-contain-1/Overview.bs

@@ -12,7 +12,7 @@ Previous Version: https://www.w3.org/TR/2017/WD-css-contain-1-20170221/
 Editor: Tab Atkins, Google, http://xanthir.com/contact/, w3cid 42199
 Editor: Florian Rivoal, On behalf of Bloomberg, https://florian.rivoal.net/, w3cid 43241
 Abstract: This CSS module describes the 'contain' property, which indicates that the element's subtree is independent of the rest of the page. This enables heavy optimizations by user agents when used well.
-Ignored Terms: scrollWidth, scrollHeight, clientWidth, clientHeight, formatting context
+Ignored Terms: scrollWidth, scrollHeight, clientWidth, clientHeight
 Link Defaults: css-lists-3 (property) counter-increment
 </pre>
 <pre class="anchors">
@@ -213,10 +213,11 @@ Layout Containment</h3>
 	If the element does not generate a <a>principal box</a> (as is the case with ''display: contents'' or ''display: none''),
 	or if the element is an <a spec="css-display-3">internal table element</a> other than ''display: table-cell'',
 	or if the element is an <a spec="css-display-3">internal ruby element</a>,
+	or if the element's <a>principal box</a> is a <a spec="css-display-3" lt="atomic inline">non-atomic</a> <a spec="css-display-3">inline-level</a> box,
 	layout containment has no effect.
 	Otherwise, giving an element <dfn export>layout containment</dfn> has the following effects:
 
-	1. The element <a>becomes a formatting context root</a>.
+	1. The element <a>establishes a formatting context</a>.
 
 	2. If a <a>fragmentation context</a> participates in <a>layout containment</a>,
 		the first element with <a>layout containment</a>
@@ -338,6 +339,7 @@ Paint Containment</h3>
 	If the element does not generate a <a>principal box</a> (as is the case with ''display: contents'' or ''display: none''),
 	or if the element is an <a spec="css-display-3">internal table element</a> other than ''display: table-cell'',
 	or if the element is an <a spec="css-display-3">internal ruby element</a>,
+	or if the element's <a>principal box</a> is a <a spec="css-display-3" lt="atomic inline">non-atomic</a> <a spec="css-display-3">inline-level</a> box,
 	paint containment has no effect.
 	Otherwise, giving an element <dfn export>paint containment</dfn> has the following effects:
 
@@ -352,7 +354,7 @@ Paint Containment</h3>
 		<span class=note>This is as if to ''overflow: visible'' was changed to ''overflow: clip'' at used value.</span>
 	2. The element acts as a containing block for absolutely positioned and fixed positioned descendants.
 	3. The element creates a <a>stacking context</a>.
-	4. The element <a>becomes a formatting context root</a>.
+	4. The element <a>establishes a formatting context</a>.
 
 	Possible optimizations that can be enabled by <a>paint containment</a> include (but are not limited to):
 
@@ -372,19 +374,6 @@ Paint Containment</h3>
 	3. Because they are guaranteed to be stacking contexts,
 		scrolling elements can be painted into a single GPU layer.
 
-<h2 id="becoming-formatting-context">Becoming a formatting context root</h2>
-
-In some some types of containment,
-a box may need to <dfn export lt='become a formatting context root|becomes a formatting context root|becoming a formatting context root'>become a <a>formatting context</a> root</dfn>.
-If the box already establishes a <a>formatting context</a> of any kind other than an <a>inline formatting context</a>,
-this condition is satisfied.
-Otherwise, it is made to establish a <a>BFC</a> by changing its <a>inner display type</a> to ''flow-root''.
-This change happens at <a>used value</a> time,
-and does not affect the <a>computed value</a> of the 'display' property.
-
-Issue: What should we do about boxes that establish <a>ruby formatting contexts</a>?
-See some discussion here: https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-319996309
-
 
 Privacy and Security Considerations {#privsec}
 ==============================================
@@ -461,20 +450,19 @@ This appendix is <em>informative</em>.
 <a href="https://www.w3.org/TR/2017/CR-css-contain-1-20170808/">Candidate Recommendation of 8 August 2017</a></h3>
 
 <ul>
-	<li>Move the definition of "Becoming a formatting context" back to this specification
-	<li>Rename "Becoming a formatting context" to "Becoming a formatting context root".
 	<li>Clarify to which box paint containment clips.
 	<li>Move the interaction between containment and the <code>bookmark-*</code> and <code>string-set</code> properties to  [[CSS-CONTENT-3]]
 	<li>Remove the effects of style containment on the "break-*" properties.
 	<li>Move the description of the effects of containement on regions from this specification to [[CSS-REGIONS-1]].
 	<li>Clarify the effects of style scoping on counter-set and counter-increment
 	<li>Size layout and paint containment don't apply to internal ruby elements
-	<li>Size containment does not apply to non-atomic inlines
+	<li>Layout, Paint, and size containments do not apply to non-atomic inlines
 	<li>Align paint containment's behavior with overflow:clip
 	<li>Elements with size containment are monolithic
 	<li>Forced breaks area allowed in elements with layout containments, but do not propagate
 	<li>Clarify the effects of scoping to a subtree
 	<li>Clarify the effects of scoping on counters
+	<li>Editorial clarification: replace "Becoming a formatting context" (aka "Becoming a formatting context root") with "Establish a FC"
 </ul>
 
 <h3 id="2017-04-19-changes">Changes from the

css-contain-1/issues-2017-cr.html

@@ -31,7 +31,7 @@ <h1>CSS Contain Level 1 Disposition of Comments for 2017-02-21 WD</h1>
 <p>An issue can be closed as <code>Accepted</code>, <code>OutOfScope</code>,
 <code>Invalid</code>, <code>Rejected</code>, or <code>Retracted</code>.
 <code>Verified</code> indicates commentor's acceptance of the response.</p>
-        <pre class=' open' id='issue-1'>
+        <pre class='a' id='issue-1'>
 Issue 1. <a href='#issue-1'>#</a>
 Summary:  Definition of Becoming a Formating Context needs work
 From:     Oriol Brufau
@@ -45,7 +45,8 @@ <h1>CSS Contain Level 1 Disposition of Comments for 2017-02-21 WD</h1>
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-374818996'>https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-374818996</a>
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-375105710'>https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-375105710</a>
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-379156461'>https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-379156461</a>
-Open</pre>
+Closed:   Accepted
+Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-380357179'>https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-380357179</a></pre>
 <pre class='a' id='issue-2'>
 Issue 2. <a href='#issue-2'>#</a>
 Summary:  Rename Becoming a Formating Context

css-contain-1/issues-2017-cr.txt

@@ -15,7 +15,8 @@ Comment:  https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-320523481
 Comment:  https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-374818996
 Comment:  https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-375105710
 Comment:  https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-379156461
-Open
+Closed:   Accepted
+Resolved: https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-380357179
 ----
 Issue 2.
 Summary:  Rename Becoming a Formating Context