Skip to content

[css-grid][css-multicol][css-flexbox][css-tables] Proposal for Various Gap Issues #1696

Closed

Description

@fantasai

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. (#1036)

Unwinding the threads of discussions and resolutions, and discussing with several people at the F2F here, we have the following proposal:

Activity

  1. fantasai commented on Aug 4, 2017

    @fantasai
    CollaboratorAuthor

    Note: We would need to (at least temporarily, possibly permanently) maintain aliases from grid-*-gap to the unprefixed properties like we do for page-break-*, since grid layouts are deployed already.

  2. bdc-stripe commented on Aug 4, 2017

    @bdc-stripe

    I'm very sympathetic to that idea. Nitpick: does that mean we'd only have a shorthand gap property for grid (assuming we keep the aliases) ?

  3. rachelandrew commented on Aug 4, 2017

    @rachelandrew
    Contributor

    I'd be happy with that as long as we have the aliasing and I think authors would be very keen with getting these for flex.

  4. atanassov commented on Aug 4, 2017

    @atanassov
    Contributor

    @bdc-stripe, no, the gap shorthand should work for any layout that accepts gaps

  5. bdc-stripe commented on Aug 4, 2017

    @bdc-stripe

    @atanassov Ok cool (didn't see a proposal for gap).

  6. SelenIT commented on Aug 4, 2017

    @SelenIT
    Collaborator

    @fantasai, does #1036 (comment) mean that the last bullet point regarding tables has just been rejected?

  7. tabatkins commented on Aug 4, 2017

    @tabatkins
    Member

    Yes, at least for now (and probably permanently), we're not going to apply row-gap and column-gap to tables.

  8. fantasai commented on Aug 9, 2017

    @fantasai
    CollaboratorAuthor

    WG resolution: https://logs.csswg.org/irc.w3.org/css/2017-08-04/#e847329
    Proposal has been accepted, minus the tables part because nobody wants to deal with tables.

  9. fantasai commented on Aug 11, 2017

    @fantasai
    CollaboratorAuthor

    Edits checked in, closing issue. :) Expect to republish to /TR at the end of the month.

  10. yisibl commented on Nov 17, 2017

    @yisibl
    Contributor

    Please start the Flexbox 2 spec as soon as possible.

  11. zxti commented on Apr 26, 2019

    @zxti

    Hello from 2019! Is there a rough ETA for gap in flexbox?

  12. rachelandrew commented on Apr 26, 2019

    @rachelandrew
    Contributor

    @zxti gap has been specified for Flexbox. It is part of the Box Alignment specification. https://www.w3.org/TR/css-align-3/#gaps

    If you are referring to browser implementation then Firefox has already implemented this. Other browsers have not as yet, but this isn't the place to chase that. The bug for Chrome is for example here https://bugs.chromium.org/p/chromium/issues/detail?id=762679

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions