- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 16 Dec 2020 17:31:44 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `2020 Snapshot`, and agreed to the following: * `RESOLVED: Move images 3 to stable bucket` * `RESOLVED: Moving css ui 5 to stable limited test` * `RESOLVED: color l4 move to stable needs testing` * `RESOLVED: Add grid 2 to snapshot in same place as grid 1` * `RESOLVED: Publish snapshot 2020 as a note` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: 2020 Snapshot<br> <fantasai> https://lists.w3.org/Archives/Member/w3c-css-wg/2020OctDec/0105.html<br> <dael> fantasai: Last publication issue. florian and I reviewed 2020 snapshot. It is ready based on earlier discussion. We think a few specs should be added/shifted though<br> <fantasai> https://github.com/w3c/csswg-drafts/issues/4715#issuecomment-745856263<br> <dael> fantasai: If it's okay I'd like to ask WG about possible changes.<br> <chris> github: https://bugs.webkit.org/show_bug.cgi?id=149772<br> <chris> oops<br> <dael> fantasai: First is add css box module L3 to top tier since it has no new functionality. Pretty stable<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/4715#issuecomment-745856263<br> <dael> fantasai: Let's go one by one<br> <dael> Rossen_: Objections to moving box to the top?<br> <dael> Resolved: move box to the top<br> <dael> fantasai: Next [missed]<br> <dael> fantasai: ditto for images L3 since we cleaned that up<br> <dael> fantasai: It is now in sync with all the changes and pretty stable<br> <dael> fantasai: Not top level as top, but stable spec with limited testing<br> <fantasai> https://drafts.csswg.org/css-2020/<br> <dael> Rossen_: Objections to moving images 3 to stable bucket?<br> <dael> RESOLVED: Move images 3 to stable bucket<br> <dael> Rossen_: Moving css ui 5 to stable limited test<br> <dael> RESOLVED: Moving css ui 5 to stable limited test<br> <dael> fantasai: Next few less sure<br> <fantasai> s/ui 5/sizing 3/<br> <fantasai> s/ui 5/sizing 3/<br> <dael> fantasai: There was an issue against snapshot about transforms l2 to rough interop bucket<br> <dael> chris: It has one impl<br> <dael> chris: Chrome has a bug on it<br> <dael> fantasai: transforms 2 I thought multi impl of 3d transforms<br> <dael> chris: Yes, but single transform is only one impl<br> <dael> florian: Seems short for rough interop<br> <dael> fantasai: Could add and exclude those bits or save for next year<br> <dael> florian: Save it<br> <dael> fantasai: Other was color adjust 1. Maybe save for next year as well<br> <emilio> hmm, Gecko ships individual transform properties iirc<br> <dael> chris: Doesn't have any tests so claim of interop is hard to substantiate. Is it only human testable?<br> <dael> fantasai: SHouldn't require human interaction to work. We can do it next year<br> <dael> fantasai: I asked about color and font 4<br> <dael> chris: I responded.<br> <dael> Rossen_: 2021<br> <gsnedders> WebKit has an impl, but not shipped in Safari<br> <dael> chris: Color 4 is stable. A few bits are not. Closed enough that I expect cr in jan or feb. stable and getting impl<br> <gsnedders> s/an impl/an impl of individual transform properties/<br> <dael> fantasai: color 4 in stable needs testing or save for 2021<br> <dael> chris: let's say stable and needs testing.<br> <dael> chris: Same with fonts 4<br> <dael> Rossen_: color l4 move to sable needs testing<br> <dael> RESOLVED: color l4 move to stable needs testing<br> <dael> fantasai: fonts 4 a lot of open issues. Lot of impl happeneing but spec text mayne not stable<br> <gsnedders> do we not have tests for most of color l4 in WPT from when impls implemented it?<br> <dael> chris: It is. I disagree on issue. 2 groups of long running issues. generic font families and privacy issues. It's stable apart from those bits.<br> <dael> florian: There are 76 open issues. Are they all what you said?<br> <dael> chris: At least 3/4 of them<br> <dael> Rossen_: Seems a little early with number of issues<br> <dael> chris: I'll push a little but I'll fallback with graceful degredation<br> <dael> fantasai: I think we want to save that for next year<br> <dael> chris: Fine<br> <dael> fantasai: Prop publishing the snapshot 2020 as a note<br> <dael> chris: Grid 2<br> <dael> fantasai: Oh, yes. Grid 1 is rough interop but needs more testing. Grid 2 is a superset of 1.<br> <dael> fantasai: Part that's different in L2 has had no issues<br> <dael> fantasai: Might make sense to put them in the same bucket<br> <dael> chris: Makes sense to me<br> <fantasai> s/same bucket/same bucket, since what's holding 2 back is the shared part/<br> <dael> Rossen_: Publishing snapshot as a note. Objections?<br> <fantasai> s/bucket/bucket as 1/<br> <dael> fantasai: Didn't resolve on grid 2.<br> <dael> Rossen_: I thought we were not going to move<br> <dael> fantasai: Add to snapshot in same place as grid 1<br> <dael> Rossen_: Objections?<br> <dael> RESOLVED: Add grid 2 to snapshot in same place as grid 1<br> <dael> Rossen_: And now, are we ready to push snapshot 2020 as a note?<br> <dael> RESOLVED: Publish snapshot 2020 as a note<br> <dael> chris: What state is it in and when to prepare for publication?<br> <dael> fantasai: Need to make resolution edits. Tomorrow, I'm guessing<br> <dael> Rossen_: Anything else for publication?<br> <dael> fantasai: That's all I got<br> <dael> florian: I'm done<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4715#issuecomment-746689122 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 16 December 2020 17:31:46 UTC