Bug 104125 - [CSS Grid Layout] Support track breadth mincontent and maxcontent
Summary: [CSS Grid Layout] Support track breadth mincontent and maxcontent
Status: RESOLVED DUPLICATE of bug 103311
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 528+ (Nightly build)
Hardware: All All
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on: 104747
Blocks: 60731
  Show dependency tree / graph
 
Reported: 2012-12-05 07:58 PST by Julien Chaffraix
Modified: 2013-02-22 13:17 PST (History)
4 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Julien Chaffraix 2012-12-05 07:58:30 PST 
The grammar allows track breadth to be mincontent or maxcontent which we don't handle properly.
Comment 1 Tony Chang 2012-12-05 12:20:16 PST 
The spec says min-content and max-content.  We already support -webkit-min-content and -webkit-max-content for things like height and width.

I suspect what we should do is add min-content and max-content support for places where we already support -webkit-min-content and -webkit-max-content and only support min-content and max-content for grid.  Then we can someday drop support for the -webkit prefix versions.
Comment 2 Julien Chaffraix 2012-12-11 17:19:57 PST 
(In reply to comment #1)
> The spec says min-content and max-content.  We already support -webkit-min-content and -webkit-max-content for things like height and width.
> 
> I suspect what we should do is add min-content and max-content support for places where we already support -webkit-min-content and -webkit-max-content and only support min-content and max-content for grid.  Then we can someday drop support for the -webkit prefix versions.

We discussed this further with Tony and agreed to use the existing prefixed version, under the contract that we should also unprefix them when we unprefix grid.
Comment 3 Julien Chaffraix 2013-02-22 13:17:08 PST 
This was handled as part of the more general bug 103311 (handle minmax track sizing).

*** This bug has been marked as a duplicate of bug 103311 ***