CINXE.COM
CSS Contain Level 1 Disposition of Comments for 2020-12-22 REC
<!DOCTYPE html> <meta charset="utf-8"> <title>CSS Contain Level 1 Disposition of Comments for 2020-12-22 REC</title> <style> .a { background: lightgreen } .d { background: lightblue } .r { background: orange } .fo { background: red } .open { border: solid red; padding: 0.2em; } :target { box-shadow: 0.25em 0.25em 0.25em; } </style> <h1>CSS Contain Level 1 Disposition of Comments for 2020-12-22 REC</h1> <p>Review document: <a href="https://www.w3.org/TR/2020/REC-css-contain-1-20201222">https://www.w3.org/TR/2020/REC-css-contain-1-20201222</a> <p>Editor's draft: <a href="http://dev.w3.org/csswg/css-contain-1/">http://dev.w3.org/csswg/css-contain-1/</a></p> None <p>The following color coding convention is used for comments:</p> <ul> <li class="a">Accepted or Rejected and positive response <li class="r">Rejected and no response <li class="fo">Rejected and negative response <li class="d">Deferred <li class="oi">Out-of-Scope or Invalid and not verified </ul> <p class=open>Open issues are marked like this</p> <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='d' id='issue-1'> Issue 1. <a href='#issue-1'>#</a> Summary: contain:size shouldn't fragment as monolithic From: fantasai Comment: <a href='https://github.com/w3c/csswg-drafts/issues/5648'>https://github.com/w3c/csswg-drafts/issues/5648</a> Response: <a href='https://github.com/w3c/csswg-drafts/issues/5648#issuecomment-715036609'>https://github.com/w3c/csswg-drafts/issues/5648#issuecomment-715036609</a> Closed: Deferred Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/5648#issuecomment-1240034875'>https://github.com/w3c/csswg-drafts/issues/5648#issuecomment-1240034875</a></pre> <pre class='a' id='issue-2'> Issue 2. <a href='#issue-2'>#</a> Summary: Minor editorial tweaks and grammar corrections From: Chris Lilley Comment: <a href='https://github.com/w3c/csswg-drafts/issues/5806'>https://github.com/w3c/csswg-drafts/issues/5806</a> Closed: Accepted Resolved: Editorial</pre> <pre class='a' id='issue-3'> Issue 3. <a href='#issue-3'>#</a> Summary: Should css-contain-1 allow new features post publication as REC? From: Chris Lilley Comment: <a href='https://github.com/w3c/csswg-drafts/issues/5806'>https://github.com/w3c/csswg-drafts/issues/5806</a> Response: <a href='https://github.com/w3c/csswg-drafts/issues/5808#issuecomment-748575361'>https://github.com/w3c/csswg-drafts/issues/5808#issuecomment-748575361</a> Closed: Rejected Resolved: Editors' discretion Verified: <a href='https://github.com/w3c/csswg-drafts/issues/5808#event-4134236457'>https://github.com/w3c/csswg-drafts/issues/5808#event-4134236457</a></pre> <pre class='a' id='issue-4'> Issue 4. <a href='#issue-4'>#</a> Summary: :root/body viewport propagation and containment From: Rune Lillesveen Comment: <a href='https://github.com/w3c/csswg-drafts/issues/5913'>https://github.com/w3c/csswg-drafts/issues/5913</a> Closed: Accepted Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/5913#issuecomment-844290779'>https://github.com/w3c/csswg-drafts/issues/5913#issuecomment-844290779</a> (tracked in spec as Candidate Correction 3) Verified: <a href='https://github.com/w3c/csswg-drafts/issues/5808#event-4134236457'>https://github.com/w3c/csswg-drafts/issues/5808#event-4134236457</a></pre> <pre class='a' id='issue-5'> Issue 5. <a href='#issue-5'>#</a> Summary: should it be possible for an element with contain:paint to be part of a transform-style:preserve-3d scene? From: David Baron Comment: <a href='https://github.com/w3c/csswg-drafts/issues/6202'>https://github.com/w3c/csswg-drafts/issues/6202</a> Closed: Accepted Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/6202#issuecomment-857863089'>https://github.com/w3c/csswg-drafts/issues/6202#issuecomment-857863089</a> (resulted in change to other spec)</pre> <pre class='a' id='issue-6'> Issue 6. <a href='#issue-6'>#</a> Summary: paint containment vs filter effects From: Florian Rivoal Comment: <a href='https://github.com/w3c/csswg-drafts/issues/6325'>https://github.com/w3c/csswg-drafts/issues/6325</a> Closed: Accepted Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/6325#issuecomment-866993550'>https://github.com/w3c/csswg-drafts/issues/6325#issuecomment-866993550</a> (editorial)</pre> <pre class='a' id='issue-7'> Issue 7. <a href='#issue-7'>#</a> Summary: Are intrinsic sizing keywords definite with size containment? From: Oriol Brufau Comment: <a href='https://github.com/w3c/csswg-drafts/issues/7206'>https://github.com/w3c/csswg-drafts/issues/7206</a> Closed: Accepted Resolved: <a href='https://github.com/w3c/csswg-drafts/issues/7206#issuecomment-1218266195'>https://github.com/w3c/csswg-drafts/issues/7206#issuecomment-1218266195</a> (editorial change to another spec)</pre> <script> (function () { var sheet = document.styleSheets[0]; function addCheckbox(className) { var element = document.querySelector('*.' + className); var label = document.createElement('label'); label.innerHTML = element.innerHTML; element.innerHTML = null; var check = document.createElement('input'); check.type = 'checkbox'; if (className == 'open') { check.checked = false; sheet.insertRule('pre:not(.open)' + '{}', sheet.cssRules.length); check.onchange = function (e) { rule.style.display = this.checked ? 'none' : 'block'; } } else { check.checked = true; sheet.insertRule('pre.' + className + '{}', sheet.cssRules.length); check.onchange = function (e) { rule.style.display = this.checked ? 'block' : 'none'; } } var rule = sheet.cssRules[sheet.cssRules.length - 1]; element.appendChild(label); label.insertBefore(check, label.firstChild); } ['a', 'd', 'fo', 'oi', 'r', 'open'].forEach(addCheckbox); }()); </script>