Content-sized resolution should only happen on content-sized tracks

Source/core/rendering/style/GridLength.h

Index: Source/core/rendering/style/GridLength.h
diff --git a/Source/core/rendering/style/GridLength.h b/Source/core/rendering/style/GridLength.h
index 6ba26b92ba54bfeff887a0f1c5962e1cf2fce62c..4940bd3c2339c6c6a930b5ced71104b816178827 100644
--- a/Source/core/rendering/style/GridLength.h
+++ b/Source/core/rendering/style/GridLength.h
@@ -72,6 +72,8 @@ public:
         return m_length == o.m_length;
     }
 
+    bool isContentSized() const { return m_type == LengthType && (m_length.isAuto() || m_length.isMinContent() || m_length.isMaxContent()); }

[ojan, 2013/08/14 23:48:36]

What about fitcontent?

[Julien - ping for review, 2013/08/15 00:11:16]

It would be an issue if it applied to <track-breadth> (we test that it doesn't
apply in grid-columns-rows-get-set.html). Per CSS sizing, it only applies to
width / max-width / min-width (same for height) but we bundle it into Length
which is confusing.

[ojan, 2013/08/15 02:43:23]

Sorry if I'm rehashing things...is there a good reason for it not to apply to
track breadths?

[Julien - ping for review, 2013/08/15 18:24:07]

A reason is that it would be redundant with 'auto' (aka minmax(mincontent,
max-content)) as they both accomplish the same behavior.

+
 private:
     // Ideally we would put the 2 following fields in a union, but Length has a constructor,
     // a destructor and a copy assignment which isn't allowed.