- From: Alan Stearns <stearns@adobe.com>
- Date: Wed, 9 May 2018 00:17:08 +0000
- To: "www-style@w3.org" <www-style@w3.org>
- Message-ID: <C0D75905-B62D-4029-910A-95ED3CAB419F@adobe.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-fonts] Unknown fragment identifiers in @font-face src:
https://github.com/w3c/csswg-drafts/issues/2566
2. [css-fonts-4] [varfont] Supported variation font axes and font features are not discoverable
https://github.com/w3c/csswg-drafts/issues/520
3. [css-values] Add clamp()?
https://github.com/w3c/csswg-drafts/issues/2519
4. [css-values-4][cssom] <resolution> serializes to 'dppx', not 'x'
https://github.com/w3c/csswg-drafts/issues/2241
5. [css-ui-4] Change the pointer cursor to indicate any interactive element.
https://github.com/w3c/csswg-drafts/issues/1936
6. [cssom-view] Consider making scroll methods return promises
https://github.com/w3c/csswg-drafts/issues/1562
7. [css-transforms-1] Browsers do not implement transform attribute syntax as described by w3c
https://github.com/w3c/csswg-drafts/issues/2623
8. [css-flexbox-1] Fragmentation rules around break propagation are confusingly-written
https://github.com/w3c/csswg-drafts/issues/2614#issuecomment-385836043
9. [css-align] Rules for align/justify-self on static position of absolutely-positioned boxes need more detail
https://github.com/w3c/csswg-drafts/issues/1432#issuecomment-387153116
10. [css-grid-2] Allow minmax where max wins over min
https://github.com/w3c/csswg-drafts/issues/1102
11. 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.
12. 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.
13. 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.
14. 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.
15. 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.
16. [filter-effects-1] What is the visual effect of filter() on the document element?
https://github.com/w3c/fxtf-drafts/issues/282
17. filter should be defined to establish a containing block for fixed and absolutely positioned elements
https://github.com/w3c/fxtf-drafts/issues/11#issuecomment-360240933
18. [css-typed-om] 'fr' units cannot be used in a calc
https://github.com/w3c/css-houdini-drafts/issues/734
Thanks,
Alan
Received on Wednesday, 9 May 2018 00:17:39 UTC