[css-contain] Clarification on ink overflow

Author: frivoal

css-contain-1/Overview.bs

@@ -302,8 +302,9 @@ Layout Containment</h3>
 			and nothing gets flowed into <code>#d</code>, <code>#e</code>, or <code>#f</code>.
 		</div>
 
-	3. If the contents of the element overflow the element,
-		they must be treated as <a>ink overflow</a>.
+	3. If the computed value of the 'overflow' property is
+		either ''overflow/visible'' or ''overflow/clip'' or a combination thereof,
+		any overflow must be treated as [=ink overflow=].
 
 	4. The element acts as a containing block for absolutely positioned and fixed positioned descendants.
 
@@ -525,6 +526,7 @@ This appendix is <em>informative</em>.
 <h3 id="2018-05-24-changes">Changes from the
 <a href="https://www.w3.org/TR/2018/CR-css-contain-1-20180524/">Candidate Recommendation of 24 May 2018</a></h3>
 
+* Clarify that layout containment causes overflow to be treated as ink overflow only when visible (or clip)
 * Layout containment suppresses baseline alignement, but size containment does not
 * Layout containment causes the element to establish a new stacking context
 * Size containment does not apply to tables

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

@@ -101,6 +101,14 @@ <h1>CSS Contain Level 1 Disposition of Comments for 2018-05-24 CR</h1>
 Response: <a href='https://github.com/w3c/csswg-drafts/issues/2995#issuecomment-411371226'>https://github.com/w3c/csswg-drafts/issues/2995#issuecomment-411371226</a>
 Closed:   Accepted
 Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/2995#issuecomment-415094473'>https://github.com/w3c/csswg-drafts/issues/2995#issuecomment-415094473</a></pre>
+<pre class='a' id='issue-9'>
+Issue 9. <a href='#issue-9'>#</a>
+Summary:  Clarify spec text about ink-overflow
+From:     Daniel Holbert
+Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3032'>https://github.com/w3c/csswg-drafts/issues/3032</a>
+Response: <a href='https://github.com/w3c/csswg-drafts/issues/3023#issuecomment-413883793'>https://github.com/w3c/csswg-drafts/issues/3023#issuecomment-413883793</a>
+Closed:   Accepted
+Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/3023#issuecomment-417016569'>https://github.com/w3c/csswg-drafts/issues/3023#issuecomment-417016569</a></pre>
 <script>
 (function () {
     var sheet = document.styleSheets[0];

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

@@ -71,3 +71,11 @@ Comment:  https://github.com/w3c/csswg-drafts/issues/2995#issuecomment-411126837
 Response: https://github.com/w3c/csswg-drafts/issues/2995#issuecomment-411371226
 Closed:   Accepted
 Resolved: https://github.com/w3c/csswg-drafts/issues/2995#issuecomment-415094473
+----
+Issue 9.
+Summary:  Clarify spec text about ink-overflow
+From:     Daniel Holbert
+Comment:  https://github.com/w3c/csswg-drafts/issues/3032
+Response: https://github.com/w3c/csswg-drafts/issues/3023#issuecomment-413883793
+Closed:   Accepted
+Resolved: https://github.com/w3c/csswg-drafts/issues/3023#issuecomment-417016569