forked from mirrors/gecko-dev
28911ca45a
Automatic update from web-platform-tests Truncate margin struts in parallel flows. We used to let trailing margins from content inside a node past its block-end affect the positioning of resumed content in the main flow. This looked ridiculous, and was even dangerous in some cases: if a resumed (non-formatting-context-establishing) block container got pushed down when resuming, we'd abort layout with kBfcBlockOffsetResolved, which would trigger removal of all previous layout results in NGBlockNode::FinishLayout(), which in turn would eventually end in invalid Vector operations, since we used to have a result there from a previous fragmentainer that should have been left alone. Bug: 1378039 Change-Id: Ib215e16acfcdfed1ed2e9b08c750cb12a3de3ec2 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/3991011 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/main@{#1065409} -- wpt-commits: cd12a2545b4dbca308b524295cb227ac3a0ae3ab wpt-pr: 36719
11 lines
397 B
HTML
11 lines
397 B
HTML
<!DOCTYPE html>
|
|
<link rel="author" title="Morten Stenshorne" href="mailto:mstensho@chromium.org">
|
|
<link rel="help" href="https://bugs.chromium.org/p/chromium/issues/detail?id=1378039">
|
|
<!DOCTYPE html>
|
|
<div style="columns:4; height:10px;">
|
|
<div style="max-height:0;">
|
|
<br>
|
|
<ol style="border-top:100px dashed; height:0;"><br></ol>
|
|
</div>
|
|
<div style="margin-top:1px;"><br></div>
|
|
</div>
|