- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 01 Oct 2025 16:09:24 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Republishing Tasks Permathread`, and agreed to the following: * `RESOLVED: Publish FPWD of anchor-position-2` * `RESOLVED: Publish new WD of css-display-4` * `RESOLVED: Publish new WD of Web Animations 2` <details><summary>The full IRC log of that discussion</summary> <kbabbitt> astearns: FPWD of anchor-position-2<br> <kbabbitt> astearns: anyone want to summarize/promote?<br> <TabAtkins> Right now, it's just the new CQs<br> <kbabbitt> fantasai: I asked for an extra week but then forgot to review<br> <kbabbitt> astearns: it only has the new CQ stuff<br> <kbabbitt> ... the argument against publishing is if someone is going to object to working on the CQ things<br> <kbabbitt> ... fantasai do you need a week to consider?<br> <kbabbitt> fantasai: I think it's fine. We should do some kind of query thing, wish we could do something better, but this is where it's at<br> <kbabbitt> astearns: Proposed resolution: Publish FPWD of anchor-position-2<br> <kbabbitt> ... continue working on CQs for anchor positioning<br> <kbabbitt> RESOLVED: Publish FPWD of anchor-position-2<br> <kbabbitt> astearns: Republish css-display<br> <kbabbitt> rachelandrew: I put it on May, another one came up<br> <kbabbitt> ... resolutions to add source-order and reading-order<br> <kbabbitt> ... which are now in Chrome<br> <kbabbitt> ... would be good to have in published spec<br> <kbabbitt> ... not aware of anything else<br> <kbabbitt> astearns: and this is a regular WD?<br> <kbabbitt> rachelandrew: YES<br> <kbabbitt> astearns: concerns or questions?<br> <kbabbitt> ... Proposed: Publish new WD of css-display-4<br> <kbabbitt> RESOLVED: Publish new WD of css-display-4<br> <kbabbitt> astearns: Updated WD of Web Animations 2<br> <kbabbitt> ydaniv: this is mostly to publish changes made for scroll animations<br> <kbabbitt> astearns: any concerns?<br> <flackr> q+<br> <astearns> ack flackr<br> <kbabbitt> flackr: no concerns with publishing scroll animations additions, however animation triggers are also in the same spec<br> <kbabbitt> ... I believe based on upcoming discussions might change significantly<br> <kbabbitt> ... is that a risk or okay to publish?<br> <kbabbitt> fantasai: we can mark an issue that we expect changes<br> <kbabbitt> astearns: or not worry too much and publish another WD with those changes<br> <kbabbitt> flackr: just wanted to call out scroll triggers is in there and likely to change<br> <kbabbitt> astearns: Proposed: New WD of Web Animations 2<br> <kbabbitt> ... will leave to editor discretion on whether to add something noting scroll triggers is early days<br> <kbabbitt> ... objections?<br> <kbabbitt> RESOLVED: Publish new WD of Web Animations 2<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6900#issuecomment-3357121086 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 1 October 2025 16:09:25 UTC