[css-overflow-3][css-backgrounds-3][css-writing-modes] Don't propagate from 'display: none' elements. Do propagate from 'display: contents' elements. #3779

fantasai · fantasai · commit 52346aba9ea4 · 2021-04-08T00:40:55.000-07:00
diff --git a/css-backgrounds-3/Overview.bs b/css-backgrounds-3/Overview.bs
@@ -1260,14 +1260,9 @@ in order to allow styling of the canvas
 CSS propagates the background of the root element
 (or, in the case of HTML, the &lt;body&gt; element)
 as described below.
-However, if no boxes are generated for the element whose background
-would be used for the canvas
-(for example, if the root element has ''display: none''),
-then the canvas background is transparent.
-
-<p class=note>Note that an element might be invisible, but still generate boxes.
-For example, if the element has ''visibility: hidden'' but not ''display: none'',
-boxes <em>are</em> generated for it and its background <em>is</em> used for the canvas.
+However, the element whose background would be used for the canvas
+is ''display: none'',
+then the [=canvas background=] is transparent.
 
 <p>If the [=canvas background=] is not opaque,
 the <dfn export>canvas surface</dfn> below it shows through.
@@ -3040,6 +3035,16 @@ The lists below describe which features from this specification are in each leve
 <h2 id="changes">
 Changes</h2>
 
+<h3 id="changes-2020-12">
+Changes since the 22 December 2020 Candidate Recommendation Snapshot</h3>
+
+<ul>
+  <li>Clarified that the rule about not propagating backgrounds from the root
+    when it doesn't generate boxes only applies to ''display: none'',
+    not ''display: contents''.
+    (<a href="https://github.com/w3c/csswg-drafts/issues/3779">Issue 3779</a>)
+</ul>
+
 <h3 id="changes-2017-10">
 Changes since the 17 October 2017 Candidate Recommendation</h3>
 
diff --git a/css-overflow-3/Overview.bs b/css-overflow-3/Overview.bs
@@ -555,22 +555,19 @@ Expanding Clipping Bounds: the 'overflow-clip-margin' property</h3>
 Overflow Viewport Propagation</h3>
 
 	UAs must apply the 'overflow-*' values
-	set on the root element to the <a>viewport</a>.
+	set on the root element to the <a>viewport</a>
+	when the root element’s 'display' value is not ''none''.
 	However,
 	when the root element is an [[!HTML]] <{html}> element
 	(including <a href="https://html.spec.whatwg.org/multipage/introduction.html#html-vs-xhtml">XML syntax for HTML</a>)
 	whose 'overflow' value is ''overflow/visible'' (in both axes),
-	and that element has a <{body}> element as a child,
+	and that element has as a child
+	a <{body}> element whose 'display' value is also not ''none'',
 	user agents must instead apply the 'overflow-*' values
 	of the first such child element to the viewport.
 	The element from which the value is propagated must then have
 	a used 'overflow' value of ''overflow/visible''.
 
-	The overflow values are not propagated to the viewport if no boxes are
-	generated for the element whose overflow values
-	would be used for the viewport (for example, if the root element has
-	display: none).
-
 	If ''overflow/visible'' is applied to the viewport,
 	it must be interpreted as ''overflow/auto''.
 	If ''overflow/clip'' is applied to the viewport,
diff --git a/css-writing-modes-3/Overview.bs b/css-writing-modes-3/Overview.bs
@@ -8,12 +8,7 @@ Work Status: Testing
 Group: csswg
 ED: https://drafts.csswg.org/css-writing-modes-3/
 TR: https://www.w3.org/TR/css-writing-modes-3/
-Previous Version: https://www.w3.org/TR/2019/PR-css-writing-modes-3-20191024/
-Previous Version: https://www.w3.org/TR/2019/CR-css-writing-modes-3-20190903/
-Previous Version: https://www.w3.org/TR/2019/CR-css-writing-modes-3-20190730/
-Previous Version: https://www.w3.org/TR/2018/CR-css-writing-modes-3-20180524/
-Previous Version: https://www.w3.org/TR/2017/CR-css-writing-modes-3-20171207/
-Previous Version: https://www.w3.org/TR/2015/CR-css-writing-modes-3-20151215/
+Previous Version: https://www.w3.org/TR/2019/REC-css-writing-modes-3-20191210/
 Issue Tracking: Tracker http://www.w3.org/Style/CSS/Tracker/products/30
 Editor: Elika J. Etemad / fantasai, Invited Expert, http://fantasai.inkedblade.net/contact, w3cid 35400
 Editor: Koji Ishii, Google, kojiishi@gmail.com, w3cid 45369
@@ -23,6 +18,7 @@ Former Editor: Michel Suignard, Microsoft, michelsu@microsoft.com
 Abstract: CSS Writing Modes Level 3 defines CSS support for various writing modes and their combinations, including left-to-right and right-to-left text ordering as well as horizontal and vertical orientations.
 Ignored Terms: glyph orientation, *-left, *-right, *-top, *-bottom, text-combine-mode, root inline box, … message topic …, glyph-orientation-horizontal
 Link Defaults: css2 (property) display/min-height/max-height/min-width/max-width/clip/left/right/bottom/top, css-text-3 (property) letter-spacing, css-text-decor-3 (property) text-decoration, svg2 (property) glyph-orientation-vertical/glyph-orientation-horizontal
+Status Text: <div class=correction><a href="https://www.w3.org/Consortium/Process/#candidate-correction">Candidate corrections</a> are marked in the document.</div>
 </pre>
 <pre class=link-defaults>
 spec:css2; type:property; text:float
@@ -2265,7 +2261,8 @@ The Principal Writing Mode</h2>
   and the default <a>page progression</a> direction.
 
   <p>As a special case for handling HTML documents,
-  if the root element has a <{body}> child element [[!HTML]],
+  if the root element has a <{body}> child element [[!HTML]]
+  <ins cite="#correction-display-none-propagation">whose 'display' value is not ''none''</ins>,
   the [=used value=] of the of 'writing-mode' and 'direction' properties on root element
   are taken
   from the [=computed value|computed=] 'writing-mode' and 'direction'
@@ -2274,6 +2271,14 @@ The Principal Writing Mode</h2>
   Note that this does not affect the computed values of 'writing-mode', 'direction', or 'text-orientation'
   of the root element itself.
 
+  <div class=correction id=correction-display-none-propagation>
+    <span class=marker>Candidate Correction 1:</span>
+    Specify that the <{body}> element is ignored for determining the [=principal writing mode=]
+    if it has ''display: none''.
+    <a href="https://github.com/w3c/csswg-drafts/issues/3779">Issue 3779</a>
+    <!-- Say that we have tests for this and point to them once we have tests for this. -->
+  </div>
+
   Note: Propagation is done on used values rather than computed values
   to avoid disrupting other aspects of style computation,
   such as [=inheritance=],
@@ -2507,130 +2512,19 @@ Privacy and Security Considerations {#priv-sec}
 
 <h2 class="no-num" id="changes">Changes</h2>
 
+  See also <a href="https://www.w3.org/TR/2019/REC-css-writing-modes-3-20191210/#changes">list of changes during Candidate Recommendation</a>.
+
   <h3 class="no-num" id="changes-2019">
   Changes since the <a href="https://www.w3.org/TR/2019/REC-css-writing-modes-3-20191210/">December
   2019 CSS Writing Modes Module Level 4 Recommendation</a></h3>
 
   <ul class="informative">
+    <li>Specified that a ''display: none'' <{body}> element does not influence the [=principal writing mode=].
+      (<a href="https://github.com/w3c/csswg-drafts/issues/3779">Issue 3779</a>)
     <li>Updated “Applies to” line for 'text-combine-upright' to mention text
       (since certain effects like ''display: contents'' can strip the box itself).
   </ul>
 
-  <h3 class="no-num" id="changes-20190903">
-  Changes since the <a href="https://www.w3.org/TR/2019/CR-css-writing-modes-3-20190903">September
-  2019 CSS Writing Modes Module Level 3 Candidate Recommendation</a></h3>
-
-  <ul>
-    <li>Clarified that the [=central baseline=] is the [=ideographic central baseline=].
-      (<a href="https://github.com/w3c/csswg-drafts/issues/5177">Issue 5177</a>)
-  </ul>
-
-  <h3 class="no-num" id="changes-20190903">
-  Changes since the <a href="https://www.w3.org/TR/2019/CR-css-writing-modes-3-20190903">September
-  2019 CSS Writing Modes Module Level 3 Candidate Recommendation</a></h3>
-
-  No substantive change;
-  minor editorial fixes
-  (see issue <a href="https://github.com/w3c/csswg-drafts/issues/4293">4293</a>,
-  <a href="https://github.com/w3c/csswg-drafts/issues/4272">4272</a>,
-  and <a href="https://github.com/w3c/csswg-drafts/issues/4273">4273</a>).
-
-  <h3 class="no-num" id="changes-20190730">
-  Changes since the <a href="https://www.w3.org/TR/2019/CR-css-writing-modes-3-20190730/">July
-  2019 CSS Writing Modes Module Level 3 Candidate Recommendation</a></h3>
-
-  <ul>
-    <li>Added back accidentally-dropped rules for sizing [=orthogonal flows=].
-      Updated wording to use current [[css-sizing-3]] terminology.
-      (<a href="https://github.com/w3c/csswg-drafts/issues/4220">Issue 4220</a>)
-  </ul>
-
-  <h3 class="no-num" id="changes-201805">
-  Changes since the <a href="https://www.w3.org/TR/2018/CR-css-writing-modes-3-20180524/">May
-  2018 CSS Writing Modes Module Level 3 Candidate Recommendation</a></h3>
-
-  <ul>
-    <li>Clarified that propagation of the principal writing mode from the body element
-        to the initial containing block and viewport
-        does affect the used value on root element as well,
-        but not its computed value.
-        Also, optionally allow propagating 'text-orientation' as well.
-        (<a href="https://github.com/w3c/csswg-drafts/issues/3066">Issue 3066</a>)
-    <li>Make the processing of white space
-        in a 'text-combine-upright' combined text sequence
-        explicitly undefined in this level
-        (<a href="https://github.com/w3c/csswg-drafts/issues/4139">Issue 4139</a>)
-        <blockquote>
-          <p>When combining text as for ''text-combine-upright: all'',
-          the glyphs of the combined text are <a>bidi-isolated</a>
-          and composed horizontally
-          (ignoring 'letter-spacing' and any forced line breaks,
-          but using the specified font settings),
-          similar to the contents of an ''inline-block'' box
-          with a [=horizontal writing mode=] and a 'line-height' of ''1em''.
-          <ins>Processing of [=document white space=] included in the combined text
-          is not defined in this level.</ins>
-        </blockquote>
-  </ul>
-
-  <h3 class="no-num" id="changes-201712">
-  Changes since the <a href="https://www.w3.org/TR/2017/CR-css-writing-modes-3-20171207/">December
-  2017 CSS Writing Modes Module Level 3 Candidate Recommendation</a></h3>
-
-  <ul>
-    <li>Fixed the fallback “available space” for orthogonal flows
-        to handle 'max-height' (and 'min-height') which it forgot to consider.
-        (<a href="https://github.com/w3c/csswg-drafts/issues/2239">Issue 2239</a>)
-  </ul>
-
-  <h3 class="no-num" id="changes-201512">
-  Changes since the <a href="http://www.w3.org/TR/2015/CR-css-writing-modes-3-20151215/">December
-  2015 CSS Writing Modes Module Level 3 Candidate Recommendation</a></h3>
-
-  <ul>
-    <li>Deferred the ''sideways-lr'' and ''sideways-rl'' values of 'writing-mode' to Level 4.
-    <li>Deferred the ''digits'' value of 'text-combine-upright' to Level 4.
-    <li>Deferred the automatic multi-column behavior of orthogonal flows to Level 4.
-    <li>Changed the fallback “available space” for orthogonal flows
-        to use the nearest fixed-size <a>scrollport</a> where available.
-        (<a href="https://github.com/w3c/csswg-drafts/issues/1391">Issue 1391</a>)
-    <li>Added Privacy and Security Considerations section.
-    <li>Miscellaneous editorial clarifications.
-  </ul>
-
-  A <a href="https://drafts.csswg.org/css-writing-modes-3/issues-cr-2015">Disposition of Comments</a> is available.
-
-  <h3 class="no-num" id="changes-201311">
-  Changes since the <a href="https://www.w3.org/TR/2014/CR-css-writing-modes-3-20140320/">March
-  2014 CSS Writing Modes Module Level 3 Candidate Recommendation</a></h3>
-
-  <ul>
-    <li>Fixed orthogonal flows auto-sizing rules to better handle shrink-wrapping.
-    <li>Removed ''sideways-left'' and ''sideways-right'' value of 'text-orientation',
-        redefined ''sideways'' to behave as ''sideways-right'',
-        and added ''sideways-lr'' and ''sideways-rl'' values to 'writing-mode' for usage with non-vertical writing systems.
-        (See <a href="http://www.w3.org/mid/55982414.1080905@inkedblade.net">discussion</a>.)
-    <li>Removed ''use-glyph-orientation'' value of 'text-orientation' and defined 'glyph-orientation-vertical' as an alias of 'text-orientation'
-      consistent with how CSS aliases are handled (see 'page-break-inside' for an example).
-    <li>
-      Added handling of degrees as integers in 'glyph-orientation-vertical',
-      as required for SVG backwards-compatibility.
-    <li>
-      Removed statements about ''run-in'' boxes, since this value was removed from CSS2.1 and has a substantially different model in CSS Display Level 3.
-      Replaced with a generalized statement about all display types, using new [[!CSS-DISPLAY-3]] terminology.
-    <li>
-      Changed to <a href="#principal-writing-mode">propagate the computed values</a> of the 'writing-mode' and the 'direction' property
-      from body child element to the initial containing block.
-    <li>
-      Changed the 'caption-side' property to <a href="#logical-direction-layout">flow-relative mappings</a>.
-    <li>
-      Specified that SVG 'writing-mode' values compute through to new equivalents.
-    <li>
-      Specified that 'writing-mode' does not apply to <a>ruby base containers</a> and <a>ruby annotation containers</a>
-    <li>
-      Made several editorial improvements and marked some features <a href="#status">at risk</a>.
-  </ul>
-
 <h2 class="no-num" id="acknowledgements">
 Acknowledgements</h2>
 
diff --git a/css-writing-modes-4/Overview.bs b/css-writing-modes-4/Overview.bs
@@ -8,6 +8,7 @@ Work Status: Testing
 Group: csswg
 ED: https://drafts.csswg.org/css-writing-modes-4/
 TR: https://www.w3.org/TR/css-writing-modes-4/
+Previous Version: https://www.w3.org/TR/2019/CR-css-writing-modes-4-20190730/
 Previous Version: https://www.w3.org/TR/2018/CR-css-writing-modes-4-20180524/
 Issue Tracking: Tracker http://www.w3.org/Style/CSS/Tracker/products/30
 Editor: Elika J. Etemad / fantasai, Invited Expert, http://fantasai.inkedblade.net/contact, w3cid 35400
@@ -2468,7 +2469,8 @@ The Principal Writing Mode</h2>
   and the default <a>page progression</a> direction.
 
   <p>As a special case for handling HTML documents,
-  if the root element has a <{body}> child element [[!HTML]],
+  if the root element has a <{body}> child element [[!HTML]]
+  whose 'display' value is not ''none'',
   the [=used value=] of the of 'writing-mode' and 'direction' properties on root element
   are taken
   from the [=computed value|computed=] 'writing-mode' and 'direction'
@@ -2793,6 +2795,10 @@ Changes since the <a href="https://www.w3.org/TR/2019/CR-css-writing-modes-4-201
 2019 CSS Writing Modes Module Level 4 Candidate Recommendation</a></h3>
 
   <ul>
+    <li>Specified that a ''display: none'' <{body}> element does not influence the [=principal writing mode=].
+      (<a href="https://github.com/w3c/csswg-drafts/issues/3779">Issue 3779</a>)
+    <li>Updated “Applies to” line for 'text-combine-upright' to mention text
+      (since certain effects like ''display: contents'' can strip the box itself).
     <li>
       Clarified that the [=central baseline=] is the [=ideographic central baseline=].
       (<a href="https://github.com/w3c/csswg-drafts/issues/5177">Issue 5177</a>)
