| Index: third_party/WebKit/LayoutTests/fast/multicol/forced-break-before-complex-margin-collapsing-expected.txt
|
| diff --git a/third_party/WebKit/LayoutTests/fast/multicol/forced-break-before-complex-margin-collapsing-expected.txt b/third_party/WebKit/LayoutTests/fast/multicol/forced-break-before-complex-margin-collapsing-expected.txt
|
| new file mode 100644
|
| index 0000000000000000000000000000000000000000..41f0b5e45ba9f7bca34aab7170f423578c81d689
|
| --- /dev/null
|
| +++ b/third_party/WebKit/LayoutTests/fast/multicol/forced-break-before-complex-margin-collapsing-expected.txt
|
| @@ -0,0 +1,12 @@
|
| +Given a parent block with a forced break before, and with an empty collapse-through child followed by a child with a top margin, check that the parent block still ends up at the exact top of the next column. The collapse-through child prevents us from correctly estimating the logical top of the parent initially.
|
| +
|
| +Below there should be a yellow box. Inside it there should be a bottom-left aligned blue box and a top-center aligned green box.
|
| +
|
| +
|
| +
|
| +
|
| +
|
| +
|
| +
|
| +
|
| +PASS
|
|
|