Bug 1657700 [wpt PR 24907] - Update tests for forced breaks at fragmentainer start., a=testonly
☠☠ backed out by a6e9c6ea61f6 ☠ ☠
authorMorten Stenshorne <mstensho@chromium.org>
Fri, 07 Aug 2020 12:46:55 +0000
changeset 543980 e87f29fb3e319c51fbd9290b8953154cf86ee4a5
parent 543979 239821d9b41e1ac72189a41b29f7c1e782a15a42
child 543981 dc0791f6390365e144390530c8c33f0817d4c916
push id123742
push userwptsync@mozilla.com
push dateFri, 07 Aug 2020 23:31:06 +0000
treeherderautoland@9584ddf5d03a [default view] [failures only]
perfherder[talos] [build metrics] [platform microbench] (compared to previous push)
reviewerstestonly
bugs1657700, 24907, 1100849, 2339663, 795604
milestone81.0a1
first release with
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Bug 1657700 [wpt PR 24907] - Update tests for forced breaks at fragmentainer start., a=testonly Automatic update from web-platform-tests Update tests for forced breaks at fragmentainer start. If there's a forced break, and it's at a valid class A breakpoint, we may break there. There's nothing in the spec suggesting otherwise. This is working correctly in the LayoutNG fragmentation engine, but not in the legacy engine (where we require some non-zero block-size content to allow forced breaks). Remove invalid tests, and add a couple of valid ones. Bug: 1100849 Change-Id: I1829a00a4e9761906ebe4536ded9c994f4737e69 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2339663 Reviewed-by: Ian Kilpatrick <ikilpatrick@chromium.org> Reviewed-by: Alison Maher <almaher@microsoft.com> Commit-Queue: Morten Stenshorne <mstensho@chromium.org> Cr-Commit-Position: refs/heads/master@{#795604} -- wpt-commits: c7c27f9106d063ad4764aacdef5cb472c4be676e wpt-pr: 24907
testing/web-platform/tests/css/css-break/forced-break-at-fragmentainer-start-000.html
testing/web-platform/tests/css/css-break/forced-break-at-fragmentainer-start-001.html
new file mode 100644
--- /dev/null
+++ b/testing/web-platform/tests/css/css-break/forced-break-at-fragmentainer-start-000.html
@@ -0,0 +1,11 @@
+<!DOCTYPE html>
+<link rel="author" title="Morten Stenshorne" href="mailto:mstensho@chromium.org">
+<link rel="help" href="https://www.w3.org/TR/css-break-3/#forced-breaks">
+<link rel="help" href="https://www.w3.org/TR/css-break-3/#unforced-breaks">
+<meta name="assert" content="A forced break at the block-start of the fragmentainer is allowed, as long as it's otherwise at a valid class A break point">
+<link rel="match" href="../reference/ref-filled-green-100px-square-only.html">
+<p>Test passes if there is a filled green square.</p>
+<div style="columns:1; column-fill:auto; width:100px; height:100px; background:green;">
+  <div style="break-after:column;"></div>
+  <div style="height:99px; background:white;"></div>
+</div>
new file mode 100644
--- /dev/null
+++ b/testing/web-platform/tests/css/css-break/forced-break-at-fragmentainer-start-001.html
@@ -0,0 +1,12 @@
+<!DOCTYPE html>
+<link rel="author" title="Morten Stenshorne" href="mailto:mstensho@chromium.org">
+<link rel="help" href="https://www.w3.org/TR/css-break-3/#forced-breaks">
+<link rel="help" href="https://www.w3.org/TR/css-break-3/#unforced-breaks">
+<meta name="assert" content="A forced break at the block-start of the fragmentainer is not allowed unless it's at a valid class A break point">
+<link rel="match" href="../reference/ref-filled-green-100px-square.xht">
+<p>Test passes if there is a filled green square and <strong>no red</strong>.</p>
+<div style="columns:2; column-fill:auto; column-gap:0; width:100px; height:100px; background:red;">
+  <div>
+    <div style="break-before:column; height:200px; background:green;"></div>
+  </div>
+</div>