W3C home > Mailing lists > Public > public-css-archive@w3.org > December 2016

[csswg-drafts] [css-containment] Clarify "must be" statements

From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
Date: Fri, 23 Dec 2016 12:15:00 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-197360152-1482495297-sysbot+gh@w3.org>
frivoal has just created a new issue for 

== [css-containment] Clarify "must be" statements ==
In a few of places, css-containment uses the phrasing "the element 
must be a &lt;foo>",
where &lt;foo> &#x2208; { **formatting context**, **stacking 

First, this is ambiguous. While it is meant as a requirement that the 
UA changes the element into being a &lt;foo> if it isn't one already, 
it could be read as implying the the effect under discussion does not 
apply if the element isn't already a &lt;foo>.

Moreover, when the element isn't a &ls;foo>, it doesn't say how to 
make it into one. When &lt;foo> is a **stacking context**, this is 
fine, as there no ambiguity how turn into one of these, but for 
**formatting context** it is a problem, as there's multiple ways an 
element could be become one, and the spec doesn't say so.

Please view or discuss this issue at 
https://github.com/w3c/csswg-drafts/issues/830 using your GitHub 
Received on Friday, 23 December 2016 12:15:01 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:06 UTC