Re: [csswg-drafts] Republishing Tasks Permathread (#6900)

The CSS Working Group just discussed `Republishing Tasks Permathread`, and agreed to the following:

* `RESOLVED: FPWD of Display 4`
* `RESOLVED: FPWD of Overflow 5`
* `RESOLVED: FPWD of Multicol 2 (as a full spec, not diff)`

<details><summary>The full IRC log of that discussion</summary>
&lt;bramus> TabAtkins: got 3 drafts alraedy were FPWD.<br>
&lt;bramus> … first one is display-4. Has two extra additions<br>
&lt;bramus> … reading-flow is actively being implemented<br>
&lt;bramus> … (missed other one)<br>
&lt;bramus> … second is overflow-5: all scroll marker stuff from flackr for carousels. talked about those at TPAC. Design is fairly stable, but might need some tweaks<br>
&lt;astearns> s/(missed other one)/interpolating display is shipped/<br>
&lt;bramus> … finally mutlicol-2 which has column pseudo.<br>
&lt;bramus> … lets just put snapping on mutlicol columns<br>
&lt;bramus> … might do rows later but dont need to wait for that for FPWD<br>
&lt;bramus> … those are the additions, and i would like to start hem being published<br>
&lt;TabAtkins> astearns: proposed reoslution: FPWD of Display 4<br>
&lt;astearns> ack fantasai<br>
&lt;TabAtkins> fantasai: sounds reasoanble for FP, there's still open issues to work on, but i think publishing makes sense<br>
&lt;TabAtkins> astearns: objectiosn?<br>
&lt;TabAtkins> RESOLVED: FPWD of Display 4<br>
&lt;TabAtkins> astearns: next, overflow 5<br>
&lt;bramus> TabAtkins: one thing: last week fantasai mentioned int needed a better intro which I still need to do and will do before publishing<br>
&lt;TabAtkins> TabAtkins: last week elika mentioned it needed a better intro, i'll write it before i hit the publish button<br>
&lt;TabAtkins> fantasai: as longa s there's an understandable intro, i think this is good for fpwd<br>
&lt;TabAtkins> astearns: so once there's an updated intro, we'll do fpwd of overflow 5<br>
&lt;TabAtkins> ChrisL: Tuesday is last day for publication, else it's next year<br>
&lt;TabAtkins> ChrisL: and there's a form<br>
&lt;bramus> TabAtkins: will do those today<br>
&lt;TabAtkins> RESOLVED: FPWD of Overflow 5<br>
&lt;rachelandrew> q+<br>
&lt;TabAtkins> astearns: last, Multicol 2<br>
&lt;TabAtkins> rachelandrew: it's currently a diff spec, was gonna copy everything from multicol 1 so i have the multicol row bit. should i do that first?<br>
&lt;TabAtkins> astearns: it's ok to have a diff spec as fpwd<br>
&lt;TabAtkins> astearns: up to editor's discrtion<br>
&lt;TabAtkins> rachelandrew: not really any changes to 1, just waiting for a test suite followup<br>
&lt;TabAtkins> fantasai: i think that would be good<br>
&lt;TabAtkins> florian: yeah, multicol 1 isn't changing fast, not much risk of drift. also yay, multicol in block direction<br>
&lt;TabAtkins> rachelandrew: i have a draft..<br>
&lt;TabAtkins> florian: me too, happy that yours is probably better developed<br>
&lt;kizu> +1 to yay for multicol in block direction<br>
&lt;TabAtkins> astearns: so proposed resolution is publish Multicol 2 as full spec FPWD<br>
&lt;TabAtkins> RESOLVED: FPWD of Multicol 2 (as a full spec, not diff)<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-2536613628 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 11 December 2024 17:23:42 UTC