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

[csswg] Agenda conf call 23-May-2018

From: Rossen Atanassov <Rossen.Atanassov@microsoft.com>
Date: Wed, 23 May 2018 02:00:44 +0000
To: "www-style@w3.org" <www-style@w3.org>
Message-ID: <CY4PR21MB015267AC0A17E876382D02399B6B0@CY4PR21MB0152.namprd21.prod.outlook.com>
Time/Phone/WebEx details available to WG Members in w3c-css-wg.
See https://lists.w3.org/Archives/Member/w3c-css-wg/2017OctDec/0076.html

US Toll Number: +1-617-324-0000

For local times, see: https://www.timeanddate.com/worldclock/fixedtime.html?iso=20180509T16

0. Extra agenda items and other digressions

1. [css-grid] Applying 'justify-content' content distribution is in the wrong place in the overall grid sizing algo

2. [css-grid] Shortcut syntax for repeat(M, 1fr)

3. [css-grid-2] Allow fr units as min

4. [css-grid-2] subgrid and grid-gap

5. [css-text-decor] Characters to skip for emphasis marks (text-emphasis)

6. [css-text-decor] Request to update css-text-decor-3 CR

7. [css-display] 'flow' inner display type should never establish a BFC

8. [css-display] Used value of display should convert flow to flow-root for BFC roots
   Issue:   https://github.com/w3c/csswg-drafts/issues/1550#issuecomment-387160020
   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.

9. [css-display] 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.

10. [css-display] 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.

11. [css-display] 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.

12. [css-text-3] word-wrap/overflow-wrap: break-word should affect min-content

13. [css-align] Rules for align/justify-self on static position of absolutely-positioned boxes need more detail

14. [css-values] Allow division of same types in calc()

15. [css-ui-4] Require link-pointer when pointer is over a link

16. [selectors-4] reconsider specificity rule for :matches()

17. [css-contain] 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.

18. [filter-effects-1] What is the visual effect of filter() on the document element?

19. filter should be defined to establish a containing block for fixed and absolutely positioned elements

Received on Wednesday, 23 May 2018 02:01:11 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:09:10 UTC