W3C home > Mailing lists > Public > www-style@w3.org > May 2018

Agenda+ [css-display-3] Open Issues / CR Transition Plan

From: fantasai <fantasai.lists@inkedblade.net>
Date: Mon, 7 May 2018 16:25:25 -0700
To: "www-style@w3.org" <www-style@w3.org>
Message-ID: <046e0431-a8c3-902b-f47c-08462812deda@inkedblade.net>
Hey everyone,

Tab and I just pushed edits to the last few issues we think needed to be addressed for CR.
The current rundown of open issues is:

Establishing independent formatting contexts
   Issue: https://github.com/w3c/csswg-drafts/issues/1457#issuecomment-380357179
   Edits: https://github.com/w3c/csswg-drafts/commit/94982e838a558e6c66516b3b13e403eae32e27ad
   New prose: https://drafts.csswg.org/css-display-3/#formatting-context
   We rewrote the definition of “formatting context” to more fully capture
   the nuances of what a formatting context is and how they interact, and
   to also define the concept of an “independent formatting context”.
   These were frequently described as a “new formatting context” but
   needed to be split out from that since inline formatting contexts are
   new but not necessarily independent.
   This effectively implements previous WG resolutions on the topic, but
   wanted to call the edits out in case anyone wanted to review them.

Used value of display should convert flow to flow-root for BFC roots
   Issue: https://github.com/w3c/csswg-drafts/issues/1550
   Edits: https://github.com/w3c/csswg-drafts/commit/0258e7ac526cffce6e81d13110ba79a681504fff
   This should be an editorial edit, just asking for WG review,
   to make sure we didn't break anything by accident.

Interaction of 'display: contents' and ::first-line
   Issue: https://github.com/w3c/csswg-drafts/issues/1310
   Proposing to defer to css-pseudo-4 to address as part of more rigorously
   defining ::first-line cascading/inheritance.

Clarify element tree definition
   Issue: https://github.com/w3c/csswg-drafts/issues/1810
   This is an editorial issue about better integration across DOM+CSS specs;
   we propose leaving it open to address later.

Clarify interaction with shadow trees
   Issue: https://github.com/w3c/csswg-drafts/issues/2365
   This is an editorial issue about better integration across DOM+CSS specs;
   we propose leaving it open to address later.

We'd like to close out the issues (preferably as described above, unless
there are problems with that) and, once the DoC and Changes section are
compiled, request a transition to CR.

~fantasai
Received on Monday, 7 May 2018 23:25:57 UTC

This archive was generated by hypermail 2.3.1 : Monday, 7 May 2018 23:25:58 UTC