Expose minContentWidth/maxContentWidth and a callback for computing them.

Expose minContentWidth/maxContentWidth and a callback for computing them.

This exposes the last hooks needed to implement flexbox layout. For now,
I didn't worry too much about the exact API we're exposing since this will
all change with the upcoming redesign (e.g. https://codereview.chromium.org/1093633002).

minContentWidth == the width if the element were to wrap at every wrapping point (not including border/padding)

maxContentWidth == the width if the element were to only wrap at hard wrapping points (e.g. \n inside a whitespace: pre).

R=eseidel@chromium.org

Committed: https://chromium.googlesource.com/external/mojo/+/636e4b166e82f9751dc530d1f1547fa0e06edc9f

[ojan, 2015-04-23 01:50:26]

ojan@chromium.org changed reviewers:
+ eseidel@chromium.org, ianh@google.com

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

lgtm

https://codereview.chromium.org/1101793003/diff/20001/sky/engine/core/dom/Ele...
File sky/engine/core/dom/Element.idl (right):

https://codereview.chromium.org/1101793003/diff/20001/sky/engine/core/dom/Ele...
sky/engine/core/dom/Element.idl:51: attribute double minContentWidth; //
Intrinsic width if all wrappable points wrap.
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]

https://codereview.chromium.org/1101793003/diff/20001/sky/engine/core/dom/Ele...
File sky/engine/core/dom/Element.idl (right):

https://codereview.chromium.org/1101793003/diff/20001/sky/engine/core/dom/Ele...
sky/engine/core/dom/Element.idl:51: attribute double minContentWidth; //
Intrinsic width if all wrappable points wrap.
On 2015/04/23 18:26:26, eseidel wrote:
> 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?

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

[ojan, 2015-04-24 20:14:45]

Committed patchset #2 (id:20001) manually as
636e4b166e82f9751dc530d1f1547fa0e06edc9f.