- From: Alan Stearns <stearns@adobe.com>
- Date: Tue, 12 May 2026 23:39:02 +0000
- To: "Cascading Style Sheets (CSS) Working Group" <www-style@w3.org>
- Message-ID: <SJ0PR02MB8514A4D3884101D12DBB9AF1B4392@SJ0PR02MB8514.namprd02.prod.outlook.com>
Time/Phone/Zoom details available to WG Members in w3c-css-wg See https://lists.w3.org/Archives/Member/w3c-css-wg/2024OctDec/0116.html https://www.timeanddate.com/worldclock/fixedtime.html?iso=20260513T16 1. [css-contain] scroll-state(stuck) CQs can easily cause flickering that is very hard to work around https://github.com/w3c/csswg-drafts/issues/13898 2. [css-color-5] light-dark() should resolve at used value time, not computed value time https://github.com/w3c/csswg-drafts/issues/13836 3. [css-overflow-5] :target-current pseudo class should also imply aria-current=true on an active scroll marker https://github.com/w3c/csswg-drafts/issues/12659 4. [selectors] Should :checked and :indeterminate be exclusive? https://github.com/w3c/csswg-drafts/issues/9706 5. [css-position][css-anchor-position] Splitting Scrollable Containing Blocks https://github.com/w3c/csswg-drafts/issues/12607 6. [css-highlights] Highlight cascade behavior for shadows is rather unfortunate. https://github.com/w3c/csswg-drafts/issues/13376 7. [css-grid-3][Masonry] Intrinsic auto repeats mixed with fixed tracks https://github.com/w3c/csswg-drafts/issues/12899 8. [css-scroll-snap-2] SnapEvent interface: Why are SnapEventInit fields optional and nullable? https://github.com/w3c/csswg-drafts/issues/13487 Note that there is one async resolution pending. Please take a look by the end of the week Proposed Resolution: Make explicit that `oblique 14deg` computes and serializes to `oblique 14deg` https://github.com/w3c/csswg-drafts/issues?q=is%3Aissue%20state%3Aopen%20label%3A%22Async%20Resolution%3A%20Call%20For%20Consensus%22 Top of scribe rota: - TabAtkins - JoshT - fantasia Thanks, Alan
Received on Tuesday, 12 May 2026 23:39:17 UTC