Expose minContentWidth/maxContentWidth and a callback for computing them.

sky/engine/core/dom/Element.idl

Index: sky/engine/core/dom/Element.idl
diff --git a/sky/engine/core/dom/Element.idl b/sky/engine/core/dom/Element.idl
index 1ad2d6f9dbbd8fb358da79065a6dee34477b41f5..957369050984c16105872b3ab14749d10a23687a 100644
--- a/sky/engine/core/dom/Element.idl
+++ b/sky/engine/core/dom/Element.idl
@@ -20,7 +20,7 @@
 
   void setNeedsLayout();
   void layout();
-  void setLayoutManager(LayoutCallback callback);
+  void setLayoutManager(LayoutCallback layout, LayoutCallback computeIntrinsicWidths);
 
   // TODO(abarth): Move to Node.
   readonly attribute CSSStyleDeclaration style;
@@ -48,4 +48,6 @@
   attribute double y;
   attribute double width;
   attribute double height;
+  attribute double minContentWidth; // Intrinsic width if all wrappable points wrap.

[eseidel, 2015/04/23 18:26:26]

So these only make sense if you have a layout manager, correct?  Should these be
tied off a separate object which is null when you don't have one?

[ojan, 2015/04/24 20:02:42]

No, they make sense for all nodes. For example, a RenderParagraph has
minContentWidth, it's just computed in the C++ code.

+  attribute double maxContentWidth; // Intrinsic width if no wrappable points wrap.
 };