- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Aug 2017 11:45:53 +0000
- To: public-css-archive@w3.org
fantasai has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-grid][css-multicol][css-flexbox][css-tables] Proposal for Various Gap Issues == We've had some feedback on gaps, the one prompting this discussion being that authors are finding it awkward that the `grid` shorthand resets the gaps, preferring that it does not and that it is treated similar to spacing controls such as grid container padding and grid item margins. (https://github.com/w3c/csswg-drafts/issues/1036) Unwinding the threads of discussions and resolutions, and discussing with several people at the F2F here, we have the following proposal: - Disconnect the `grid-gap` properties from the `grid` shorthand, resolving https://github.com/w3c/csswg-drafts/issues/1036 - Undo the [resolution](https://lists.w3.org/Archives/Public/www-style/2015Sep/0093.html) changing `column-gap` and `row-gap` to `grid-column-gap` and `grid-row-gap`. - As before that resolution, `column-gap` is shared with multi-col and `normal` computes to zero except on multi-column elements. - Apply `column-gap` and `row-gap` to flex containers, resolving a strong demand from flexbox users to have this spacing control. (See [Rachel's message to www-style](https://lists.w3.org/Archives/Public/www-style/2016Feb/0333.html) and (https://github.com/w3c/csswg-drafts/issues/592)) - As a clean-up measure, have these properties obsolete `border-spacing` (which inherits, which is weird) by having them defer to `border-spacing` when specified as `normal` and override it otherwise. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1696 using your GitHub account
Received on Friday, 4 August 2017 11:45:57 UTC