- From: Sam Davis via GitHub <noreply@w3.org>
- Date: Fri, 16 Jan 2026 17:03:32 +0000
- To: public-css-archive@w3.org
oSamDavis has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-gaps-1]: Suppression of gaps/gutters across fragment breaks with Spanning Item == In [issue 11520](https://github.com/w3c/csswg-drafts/issues/11520), we resolved to suppress gaps that overlap with a fragment break or are the last content before a break. The reasoning was that a page or fragment break already acts as a separator, which is the intended purpose of gaps. See: <img width="8258" height="3144" alt="Image" src="https://github.com/user-attachments/assets/00e4ab26-ec63-4605-b247-da71fae6dd0a" /> This issue is to propose a caveat to that resolution. In Grid layouts, a gap may overlap a fragment break while also being spanned by a spanning item. For example, Take this unfragmented grid: <img width="1074" height="983" alt="Image" src="https://github.com/user-attachments/assets/24108efd-74dd-4858-9a49-1b2d4a1348d3" /> And a fragment break occurs here: <img width="4050" height="2567" alt="Image" src="https://github.com/user-attachments/assets/4cae110e-7857-4e69-b5a7-1656467e9737" /> The result will be: <img width="11262" height="2767" alt="Image" src="https://github.com/user-attachments/assets/f9463d45-ae7e-48ea-a978-1bb71894452a" /> Suppressing the gap in such scenario would unintentionally suppress parts of the spanning item. Therefore, it makes sense to add an exception so that gaps are not suppressed when a spanning item covers the gap. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13362 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 January 2026 17:03:33 UTC