- From: Ian Kilpatrick via GitHub <noreply@w3.org>
- Date: Thu, 26 Mar 2026 20:29:30 +0000
- To: public-css-archive@w3.org
bfgeek has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-box-4] Scope margin-trim down to block & multi-column containers only? == @tabatkins , @mstensho and myself have had some discussions about applying margin-trim to flex/grid. It was resolved in https://github.com/w3c/csswg-drafts/issues/3255 to allow margin-trim to flex/grid. This issue didn't have a whole lot of discussion, and the single author comment on the issue appears a little mis-guided about what this would achieve[1]. We think it'd make more sense to make margin-trim focused on block/multi-col layout instead. The use-case for margin-trim in flex/grid doesn't really exist. The use-case for consistent spacing is solved by row-gap/column-gap (and solved it well!). In addition scoping this down to block/multi-col means that the inline-* values for margin-trim would disappear as they don't apply in these modes. [1] Wanted a progressive enhancement technique to put grid/flex in a "clean state" to use with gaps, but this isn't what margin-trim does. > That way margin-trim: all could always be used to get a clean slate when using gap for spacing. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13731 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 March 2026 20:29:31 UTC