[csswg] Agenda for conf call on Jan 31, 2024

Time/Phone/Zoom details available to WG Members in w3c-css-wg.
See https://lists.w3.org/Archives/Member/w3c-css-wg/2023JulSep/0095.html

https://www.timeanddate.com/worldclock/fixedtime.html?iso=20240228T17

0. Extra agenda items and other digressions

1. Update to CONTRIBUTING.md
https://github.com/w3c/csswg-drafts/pull/9928

2. [css-cascade] [css-nesting] Figure out whether we're fine with "shifting up" bare declarations after rules
https://github.com/w3c/csswg-drafts/issues/8738

3. [css-values-5][various] Better handling of arguments with commas
https://github.com/w3c/csswg-drafts/issues/9539

4. [css-values] Other options for value-agnostic delimiters
https://github.com/w3c/csswg-drafts/issues/6705

5. [css-values] Let B default to 1 in round(<strategy>?, A, B)
https://github.com/w3c/csswg-drafts/issues/9668

6. [css-values] Clarifying serialization of negative zero and expression simplification
https://github.com/w3c/csswg-drafts/issues/9750

7. [css-borders] accept "px" for pixel values in border-image-slice
https://github.com/w3c/csswg-drafts/issues/6739

8. [css-contain-3] Should not cq units be interpreted in the flatDom context?
https://github.com/w3c/csswg-drafts/issues/7947

9. [css-lists-3] list-item counter nesting is confusing
https://github.com/w3c/csswg-drafts/issues/9076#issuecomment-1881237182

10. [css-contain-2]: Should the first contentvisibilityautostatechange event be fired without knowing if the element is close to the viewport
https://github.com/w3c/csswg-drafts/issues/9803

Thanks,

Alan