commit 1ff147d015b3be44eb7f8744ba748fd9ebf452af
author Morten Stenshorne <mstensho@chromium.org> Fri May 24 13:37:43 2019
committer Commit Bot <commit-bot@chromium.org> Fri May 24 13:37:43 2019
tree af7a534d43728ed96e2396db14137f6a7374dba1
parent d143665d3140a1dd6d4d988ddb0c9f4f1c0cef22

[LayoutNG] OBJECTs with fallback content may not create a new FC.

Avoid false positives from DefinitelyNewFormattingContext().

If an OBJECT element ends up using its fallback content, we cannot claim
that it's going to establish a new formatting context, just by looking
at the element type. Then the OBJECT behaves just like any generic
element.

Always reporting that an OBJECT establishes a new formatting context,
allowed the parent to use LayoutNG, although the OBJECT had children
(e.g. a RUBY element) that require legacy layout. Letting NG and legacy
cooperate in the same block formatting context is something we don't
support.

Bug: 966363
Change-Id: Ica9247e9936eb1dbdfc8dabdc96cdb2afdad5bac
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1628711
Commit-Queue: Morten Stenshorne <mstensho@chromium.org>
Commit-Queue: Emil A Eklund <eae@chromium.org>
Auto-Submit: Morten Stenshorne <mstensho@chromium.org>
Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org>
Reviewed-by: Emil A Eklund <eae@chromium.org>
Cr-Commit-Position: refs/heads/master@{#663053}