The grammar allows track breadth to be mincontent or maxcontent which we don't handle properly.
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.
(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.
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 ***