CanUseNewLayout should trigger nglayout in more cases than we handle today.
CanUseNewLayout was returning false even if there were no inline children.
Ian confirmed that if there were no inline children, we should use
nglayout.
The root cause is that LayoutBlockFlow.isInline flag is initialized to true
in constructor.
It gets reset in LayoutBlockFlow::makeChildrenNonInline.
This code only gets called if at least one BlockFlow child is laid out. If all your children are absolute, this does not happen.
This change also causes 6 more existing virtual/nglayout test failures that I have not investigated.
BUG=635619
Review-Url: https://codereview.chromium.org/2444323003
Cr-Commit-Position: refs/heads/master@{#428150}
2 files changed
