diff --git a/tests/wpt/css-tests/css-break-3_dev/html/chapter-1.htm b/tests/wpt/css-tests/css-break-3_dev/html/chapter-1.htm new file mode 100644 index 00000000000..ec7e0365eed --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/html/chapter-1.htm @@ -0,0 +1,57 @@ + + + + +
+Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 1 Introduction | |||
+ + + 1.1 Module Interactions | |||
+ + + 1.2 Values |
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 2 Fragmentation Model and Terminology | |||
+ + + 2.1 Parallel Fragmentation Flows | |||
+ floats-clear-breaks-002 | += | +Ahem | +CSS Regions: forced region breaks and clear on floats inside named flow contents
+
|
+
+ floats-in-named-flow-012 | += | +Ahem | +floats with forced region breaks inside them
+
|
+
+ floats-in-named-flow-029 | += | +Ahem | +CSS Regions: margins around forced breaks when break is around float
+
|
+
+ floats-in-named-flow-030 | += | +Ahem | +CSS Regions: margins around unforced breaks when break is around float
+
|
+
+ + + 2.2 Nested Fragmentation Flows |
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 3 Controlling Breaks | |||
+ + + 3.1 Breaks Between Boxes: the ‘break-before’ and ‘break-after’ properties | |||
+ + + 3.2 Breaks Within Boxes: the ‘break-inside’ property | |||
+ + + 3.3 Breaks Between Lines: ‘orphans’, ‘widows’ | |||
+ + + 3.4 Page Break Aliases: the ‘page-break-before’, ‘page-break-after’, and ‘page-break-inside’ properties |
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 4 Rules for Breaking | |||
+ regions-transforms-013 | += = | ++ | CSS Regions: Transformed named flow (monolithic) content that breaks across multiple regions
+
|
+
+ regions-transforms-020 | += | ++ | CSS Regions: Transformed region with named flow (fragmentable) content that breaks across multiple regions
+
|
+
+ regions-transforms-013 | += = | ++ | CSS Regions: Transformed named flow (monolithic) content that breaks across multiple regions
+
|
+
+ + + 4.1 Possible Break Points | |||
+ + + 4.2 Types of Breaks | |||
+ + + 4.3 Forced Breaks | |||
+ + + 4.4 Unforced Breaks | |||
+ + + 4.5 Optimizing Unforced Breaks |
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 5 Box Model for Breaking | |||
+ + + 5.1 Breaking into Varying-size Fragmentainers | |||
+ + + 5.2 Adjoining Margins at Breaks | |||
+ floats-in-named-flow-029 | += | +Ahem | +CSS Regions: margins around forced breaks when break is around float
+
|
+
+ floats-in-named-flow-030 | += | +Ahem | +CSS Regions: margins around unforced breaks when break is around float
+
|
+
+ + + 5.3 Splitting Boxes | |||
+ + + 5.4 Fragmented Borders and Backgrounds: the ‘box-decoration-break’ property | |||
+ + + 5.4.1 Joining Boxes for ‘slice’ | |||
+ + + 5.5 Transforms, Positioning, and Pagination | |||
+ position-relative-001 | += | +Ahem | +CSS Regions: flowing content that has position: relative
+
|
+
+ regions-transforms-008 | += | +Ahem | +CSS Regions: Transformed named flow (text) content that breaks across multiple regions and overflows
+
|
+
+ regions-transforms-009 | += | +Ahem | +CSS Regions: Transformed region with named flow (text) content that breaks across multiple regions and overflows
+
|
+
+ regions-transforms-013 | += = | ++ | CSS Regions: Transformed named flow (monolithic) content that breaks across multiple regions
+
|
+
+ regions-transforms-020 | += | ++ | CSS Regions: Transformed region with named flow (fragmentable) content that breaks across multiple regions
+
|
+
+ regions-transforms-021 | += | ++ | CSS Regions: Transforms on multiple named flow (non-text) content nodes that break across multiple regions
+
|
+
+ regions-transforms-022 | += | +Ahem | +CSS Regions: Transforms on multiple named flow (text) content nodes that break across multiple regions
+
|
+
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 6 Conformance | |||
+ + + 6.1 Document Conventions | |||
+ + + 6.2 Conformance Classes | |||
+ + + 6.3 Partial Implementations | |||
+ + + 6.4 Experimental Implementations | |||
+ + + 6.5 Non-Experimental Implementations | |||
+ + + 6.6 CR Exit Criteria |
+ Test passes if you see two squares separated by a small vertical space. The squares should
+ have a black outline, the top square should be blue and the bottom one should be green.
+ You should see no red.
+
+
+
+
+ Test passes if you see two identical rows of colored squares. Each row should have three
+ squares, from left to right as follows: blue, gray, green. The squares in a row should
+ be flush to each other, but the two rows should have some space between them.
+ Test fails is you see any red.
+
+
+
+ + Test passes if you see two colored squares each inside a black-bordered rectangle: +
+
+
+
+ + Test passes if you see two colored squares each inside a black-bordered rectangle: +
+
+
+
Test passes if you see two green squares (one bigger and one smaller) and no red.
++
+
+ Test passes if you see two squares separated by a small vertical space. The squares should
+ have a black outline, the top square should be blue and the bottom one should be green.
+ You should see no red.
+
+ Test passes if you see two identical rows of colored squares. Each row should have three
+ squares, from left to right as follows: blue, gray, green. The squares in a row should
+ be flush to each other, but the two rows should have some space between them.
+ Test fails is you see any red.
+
+ + Test passes if you see two colored squares each inside a black-bordered rectangle: +
+ + Test passes if you see two colored squares each inside a black-bordered rectangle: +
Test passes if you see two green squares (one bigger and one smaller) and no red.
+The test passes if:
+The test passes if you see either two green squares or one vertical green rectangle. There should be no red.
+ + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/html/reference/regions-transforms-013-ref.htm b/tests/wpt/css-tests/css-break-3_dev/html/reference/regions-transforms-013-ref.htm new file mode 100644 index 00000000000..3e94de81be9 --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/html/reference/regions-transforms-013-ref.htm @@ -0,0 +1,21 @@ + + +The test passes if you see either two green squares or one vertical green rectangle. There should be no red.
+ + + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/html/reference/regions-transforms-020-ref.htm b/tests/wpt/css-tests/css-break-3_dev/html/reference/regions-transforms-020-ref.htm new file mode 100644 index 00000000000..1064759b018 --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/html/reference/regions-transforms-020-ref.htm @@ -0,0 +1,21 @@ + + +The test passes if you see two green squares and no red.
+ + + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/html/reftest-toc.htm b/tests/wpt/css-tests/css-break-3_dev/html/reftest-toc.htm new file mode 100644 index 00000000000..e365643ca9a --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/html/reftest-toc.htm @@ -0,0 +1,121 @@ + + + + + +Test | +Reference | +Flags | +
---|---|---|
+ floats-clear-breaks-002 | += | +Ahem | +
+ floats-in-named-flow-012 | += | +Ahem | +
+ floats-in-named-flow-029 | += | +Ahem | +
+ floats-in-named-flow-030 | += | +Ahem | +
+ position-relative-001 | += | +Ahem | +
+ regions-transforms-008 | += | +Ahem | +
+ regions-transforms-009 | += | +Ahem | +
+ regions-transforms-013 | += | ++ |
= | +||
+ regions-transforms-020 | += | ++ |
+ regions-transforms-021 | += | ++ |
+ regions-transforms-022 | += | +Ahem | +
The test passes if:
+The test passes if:
+The test passes if you see either two green squares or one vertical green rectangle. There should be no red.
+ + + + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/html/regions-transforms-020.htm b/tests/wpt/css-tests/css-break-3_dev/html/regions-transforms-020.htm new file mode 100644 index 00000000000..a6c0af09d5b --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/html/regions-transforms-020.htm @@ -0,0 +1,61 @@ + + + +The test passes if you see two green squares and no red.
+ + +The test passes if you see two green squares and no red.
+ + + + + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/html/regions-transforms-022.htm b/tests/wpt/css-tests/css-break-3_dev/html/regions-transforms-022.htm new file mode 100644 index 00000000000..e433da77ff4 --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/html/regions-transforms-022.htm @@ -0,0 +1,83 @@ + + + +The test passes if you see two green squares and no red.
+This index contains both + self-describing tests + and reftests. + A separate alphabetical reftest index + is provided for tests in reftest + format along with the reftest manifest.
+ +Chapter 1 - + Introduction | +(0 Tests) |
---|---|
Chapter 2 - + Fragmentation Model and Terminology | +(4 Tests) |
Chapter 3 - + Controlling Breaks | +(0 Tests) |
Chapter 4 - + Rules for Breaking | +(2 Tests) |
Chapter 5 - + Box Model for Breaking | +(9 Tests) |
Chapter 6 - + Conformance | +(0 Tests) |
This is a Development + version of the CSS Fragmentation Module Level 3 CR Test Suite.
+ +You can provide test data or review the testing results for this test suite:
+Some tests in the test suite may contain errors. + Please check the latest version of the + CSS Fragmentation 3 specification + and its errata + before assuming a failure is due to an implementation bug and + not a test suite bug.
+ + ++ In time we hope to correct all errors and extend this test suite to + cover all of CSS Fragmentation 3. Your help is welcome in this effort. + The appropriate mailing list for submitting tests and bug reports is + public-css-testsuite@w3.org. + More information on the contribution process and test guidelines is + available on the wiki + page.
+ +Tests are currently available in these formats:
+ +text/html
application/xhtml+xml
Unless the test instructions explicitly indicate otherwise, + any occurrence of red in a test indicates test failure.
+ +An implementation report template + is available to help with creating implementation reports. See also the + explanation + of its format.
+ +Most of the test suite makes the following assumptions:
+div
element is assigned display: block;
+ and no other property declaration.span
element is assigned display: inline;
+ and no other property declaration.p
element is assigned display: block;
li
element is assigned display: list-item;
table
, tbody
,
+ tr
, and td
are assigned the display
+ values table
, table-row-group
,
+ table-row
, and table-cell
, respectively.black
, white
, gray
,
+ silver
, red
, green
, blue
,
+ purple
, yellow
, orange
, teal
,
+ fuchsia
, maroon
, navy
, aqua
,
+ and lime
as distinct colors.In addition, some of the tests make one or more of the following + assumptions:
+ +The tests that need these assumptions to be true have not yet been + marked, but it is likely that we will add a way to identify these + tests in due course. Tests should avoid relying on these assumptions + unless necessary.
+ +This test suite is licensed under both the + W3C + Test Suite License and the W3C + 3-clause BSD License. See W3C Legal's explanation + of the licenses.
+ +Many thanks to the following for their contributions:
+This is a Development + version of the CSS Fragmentation Module Level 3 CR Test Suite.
+ +You can provide test data or review the testing results for this test suite:
+Some tests in the test suite may contain errors. + Please check the latest version of the + CSS Fragmentation 3 specification + and its errata + before assuming a failure is due to an implementation bug and + not a test suite bug.
+ + ++ In time we hope to correct all errors and extend this test suite to + cover all of CSS Fragmentation 3. Your help is welcome in this effort. + The appropriate mailing list for submitting tests and bug reports is + public-css-testsuite@w3.org. + More information on the contribution process and test guidelines is + available on the wiki + page.
+ +Tests are currently available in these formats:
+ +text/html
application/xhtml+xml
Unless the test instructions explicitly indicate otherwise, + any occurrence of red in a test indicates test failure.
+ +An implementation report template + is available to help with creating implementation reports. See also the + explanation + of its format.
+ +Most of the test suite makes the following assumptions:
+div
element is assigned display: block;
+ and no other property declaration.span
element is assigned display: inline;
+ and no other property declaration.p
element is assigned display: block;
li
element is assigned display: list-item;
table
, tbody
,
+ tr
, and td
are assigned the display
+ values table
, table-row-group
,
+ table-row
, and table-cell
, respectively.black
, white
, gray
,
+ silver
, red
, green
, blue
,
+ purple
, yellow
, orange
, teal
,
+ fuchsia
, maroon
, navy
, aqua
,
+ and lime
as distinct colors.In addition, some of the tests make one or more of the following + assumptions:
+ +The tests that need these assumptions to be true have not yet been + marked, but it is likely that we will add a way to identify these + tests in due course. Tests should avoid relying on these assumptions + unless necessary.
+ +This test suite is licensed under both the + W3C + Test Suite License and the W3C + 3-clause BSD License. See W3C Legal's explanation + of the licenses.
+ +Many thanks to the following for their contributions:
+Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 1 Introduction | |||
+ + + 1.1 Module Interactions | |||
+ + + 1.2 Values |
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 2 Fragmentation Model and Terminology | |||
+ + + 2.1 Parallel Fragmentation Flows | |||
+ floats-clear-breaks-002 | += | +Ahem | +CSS Regions: forced region breaks and clear on floats inside named flow contents
+
|
+
+ floats-in-named-flow-012 | += | +Ahem | +floats with forced region breaks inside them
+
|
+
+ floats-in-named-flow-029 | += | +Ahem | +CSS Regions: margins around forced breaks when break is around float
+
|
+
+ floats-in-named-flow-030 | += | +Ahem | +CSS Regions: margins around unforced breaks when break is around float
+
|
+
+ + + 2.2 Nested Fragmentation Flows |
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 3 Controlling Breaks | |||
+ + + 3.1 Breaks Between Boxes: the ‘break-before’ and ‘break-after’ properties | |||
+ + + 3.2 Breaks Within Boxes: the ‘break-inside’ property | |||
+ + + 3.3 Breaks Between Lines: ‘orphans’, ‘widows’ | |||
+ + + 3.4 Page Break Aliases: the ‘page-break-before’, ‘page-break-after’, and ‘page-break-inside’ properties |
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 4 Rules for Breaking | |||
+ regions-transforms-013 | += = | ++ | CSS Regions: Transformed named flow (monolithic) content that breaks across multiple regions
+
|
+
+ regions-transforms-020 | += | ++ | CSS Regions: Transformed region with named flow (fragmentable) content that breaks across multiple regions
+
|
+
+ regions-transforms-013 | += = | ++ | CSS Regions: Transformed named flow (monolithic) content that breaks across multiple regions
+
|
+
+ + + 4.1 Possible Break Points | |||
+ + + 4.2 Types of Breaks | |||
+ + + 4.3 Forced Breaks | |||
+ + + 4.4 Unforced Breaks | |||
+ + + 4.5 Optimizing Unforced Breaks |
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 5 Box Model for Breaking | |||
+ + + 5.1 Breaking into Varying-size Fragmentainers | |||
+ + + 5.2 Adjoining Margins at Breaks | |||
+ floats-in-named-flow-029 | += | +Ahem | +CSS Regions: margins around forced breaks when break is around float
+
|
+
+ floats-in-named-flow-030 | += | +Ahem | +CSS Regions: margins around unforced breaks when break is around float
+
|
+
+ + + 5.3 Splitting Boxes | |||
+ + + 5.4 Fragmented Borders and Backgrounds: the ‘box-decoration-break’ property | |||
+ + + 5.4.1 Joining Boxes for ‘slice’ | |||
+ + + 5.5 Transforms, Positioning, and Pagination | |||
+ position-relative-001 | += | +Ahem | +CSS Regions: flowing content that has position: relative
+
|
+
+ regions-transforms-008 | += | +Ahem | +CSS Regions: Transformed named flow (text) content that breaks across multiple regions and overflows
+
|
+
+ regions-transforms-009 | += | +Ahem | +CSS Regions: Transformed region with named flow (text) content that breaks across multiple regions and overflows
+
|
+
+ regions-transforms-013 | += = | ++ | CSS Regions: Transformed named flow (monolithic) content that breaks across multiple regions
+
|
+
+ regions-transforms-020 | += | ++ | CSS Regions: Transformed region with named flow (fragmentable) content that breaks across multiple regions
+
|
+
+ regions-transforms-021 | += | ++ | CSS Regions: Transforms on multiple named flow (non-text) content nodes that break across multiple regions
+
|
+
+ regions-transforms-022 | += | +Ahem | +CSS Regions: Transforms on multiple named flow (text) content nodes that break across multiple regions
+
|
+
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 6 Conformance | |||
+ + + 6.1 Document Conventions | |||
+ + + 6.2 Conformance Classes | |||
+ + + 6.3 Partial Implementations | |||
+ + + 6.4 Experimental Implementations | |||
+ + + 6.5 Non-Experimental Implementations | |||
+ + + 6.6 CR Exit Criteria |
+ Test passes if you see two squares separated by a small vertical space. The squares should
+ have a black outline, the top square should be blue and the bottom one should be green.
+ You should see no red.
+
+
+
+
+ Test passes if you see two identical rows of colored squares. Each row should have three
+ squares, from left to right as follows: blue, gray, green. The squares in a row should
+ be flush to each other, but the two rows should have some space between them.
+ Test fails is you see any red.
+
+
+
+ + Test passes if you see two colored squares each inside a black-bordered rectangle: +
+
+
+
+ + Test passes if you see two colored squares each inside a black-bordered rectangle: +
+
+
+
Test passes if you see two green squares (one bigger and one smaller) and no red.
++
+
+ Test passes if you see two squares separated by a small vertical space. The squares should
+ have a black outline, the top square should be blue and the bottom one should be green.
+ You should see no red.
+
+ Test passes if you see two identical rows of colored squares. Each row should have three
+ squares, from left to right as follows: blue, gray, green. The squares in a row should
+ be flush to each other, but the two rows should have some space between them.
+ Test fails is you see any red.
+
+ + Test passes if you see two colored squares each inside a black-bordered rectangle: +
+ + Test passes if you see two colored squares each inside a black-bordered rectangle: +
Test passes if you see two green squares (one bigger and one smaller) and no red.
+The test passes if:
+The test passes if you see either two green squares or one vertical green rectangle. There should be no red.
+ + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/xhtml1/reference/regions-transforms-013-ref.xht b/tests/wpt/css-tests/css-break-3_dev/xhtml1/reference/regions-transforms-013-ref.xht new file mode 100644 index 00000000000..5a6a3049a08 --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/xhtml1/reference/regions-transforms-013-ref.xht @@ -0,0 +1,21 @@ + + +The test passes if you see either two green squares or one vertical green rectangle. There should be no red.
+ + + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/xhtml1/reference/regions-transforms-020-ref.xht b/tests/wpt/css-tests/css-break-3_dev/xhtml1/reference/regions-transforms-020-ref.xht new file mode 100644 index 00000000000..aae13775fd8 --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/xhtml1/reference/regions-transforms-020-ref.xht @@ -0,0 +1,21 @@ + + +The test passes if you see two green squares and no red.
+ + + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/xhtml1/reftest-toc.xht b/tests/wpt/css-tests/css-break-3_dev/xhtml1/reftest-toc.xht new file mode 100644 index 00000000000..48d26f46228 --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/xhtml1/reftest-toc.xht @@ -0,0 +1,121 @@ + + + + + +Test | +Reference | +Flags | +
---|---|---|
+ floats-clear-breaks-002 | += | +Ahem | +
+ floats-in-named-flow-012 | += | +Ahem | +
+ floats-in-named-flow-029 | += | +Ahem | +
+ floats-in-named-flow-030 | += | +Ahem | +
+ position-relative-001 | += | +Ahem | +
+ regions-transforms-008 | += | +Ahem | +
+ regions-transforms-009 | += | +Ahem | +
+ regions-transforms-013 | += | ++ |
= | +||
+ regions-transforms-020 | += | ++ |
+ regions-transforms-021 | += | ++ |
+ regions-transforms-022 | += | +Ahem | +
The test passes if:
+The test passes if:
+The test passes if you see either two green squares or one vertical green rectangle. There should be no red.
+ + + + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/xhtml1/regions-transforms-020.xht b/tests/wpt/css-tests/css-break-3_dev/xhtml1/regions-transforms-020.xht new file mode 100644 index 00000000000..e0866521167 --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/xhtml1/regions-transforms-020.xht @@ -0,0 +1,61 @@ + + + +The test passes if you see two green squares and no red.
+ + +The test passes if you see two green squares and no red.
+ + + + + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/xhtml1/regions-transforms-022.xht b/tests/wpt/css-tests/css-break-3_dev/xhtml1/regions-transforms-022.xht new file mode 100644 index 00000000000..0836a17cd7d --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/xhtml1/regions-transforms-022.xht @@ -0,0 +1,83 @@ + + + +The test passes if you see two green squares and no red.
+This index contains both + self-describing tests + and reftests. + A separate alphabetical reftest index + is provided for tests in reftest + format along with the reftest manifest.
+ +Chapter 1 - + Introduction | +(0 Tests) |
---|---|
Chapter 2 - + Fragmentation Model and Terminology | +(4 Tests) |
Chapter 3 - + Controlling Breaks | +(0 Tests) |
Chapter 4 - + Rules for Breaking | +(2 Tests) |
Chapter 5 - + Box Model for Breaking | +(9 Tests) |
Chapter 6 - + Conformance | +(0 Tests) |
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 1 Introduction | |||
+ + + 1.1 Module Interactions | |||
+ + + 1.2 Values |
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 2 Fragmentation Model and Terminology | |||
+ + + 2.1 Parallel Fragmentation Flows | |||
+ floats-clear-breaks-002 | += | +Ahem | +CSS Regions: forced region breaks and clear on floats inside named flow contents
+
|
+
+ floats-in-named-flow-012 | += | +Ahem | +floats with forced region breaks inside them
+
|
+
+ floats-in-named-flow-029 | += | +Ahem | +CSS Regions: margins around forced breaks when break is around float
+
|
+
+ floats-in-named-flow-030 | += | +Ahem | +CSS Regions: margins around unforced breaks when break is around float
+
|
+
+ + + 2.2 Nested Fragmentation Flows |
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 3 Controlling Breaks | |||
+ + + 3.1 Breaks Between Boxes: the ‘break-before’ and ‘break-after’ properties | |||
+ + + 3.2 Breaks Within Boxes: the ‘break-inside’ property | |||
+ + + 3.3 Breaks Between Lines: ‘orphans’, ‘widows’ | |||
+ + + 3.4 Page Break Aliases: the ‘page-break-before’, ‘page-break-after’, and ‘page-break-inside’ properties |
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 4 Rules for Breaking | |||
+ regions-transforms-013 | += = | ++ | CSS Regions: Transformed named flow (monolithic) content that breaks across multiple regions
+
|
+
+ regions-transforms-020 | += | ++ | CSS Regions: Transformed region with named flow (fragmentable) content that breaks across multiple regions
+
|
+
+ regions-transforms-013 | += = | ++ | CSS Regions: Transformed named flow (monolithic) content that breaks across multiple regions
+
|
+
+ + + 4.1 Possible Break Points | |||
+ + + 4.2 Types of Breaks | |||
+ + + 4.3 Forced Breaks | |||
+ + + 4.4 Unforced Breaks | |||
+ + + 4.5 Optimizing Unforced Breaks |
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 5 Box Model for Breaking | |||
+ + + 5.1 Breaking into Varying-size Fragmentainers | |||
+ + + 5.2 Adjoining Margins at Breaks | |||
+ floats-in-named-flow-029 | += | +Ahem | +CSS Regions: margins around forced breaks when break is around float
+
|
+
+ floats-in-named-flow-030 | += | +Ahem | +CSS Regions: margins around unforced breaks when break is around float
+
|
+
+ + + 5.3 Splitting Boxes | |||
+ + + 5.4 Fragmented Borders and Backgrounds: the ‘box-decoration-break’ property | |||
+ + + 5.4.1 Joining Boxes for ‘slice’ | |||
+ + + 5.5 Transforms, Positioning, and Pagination | |||
+ position-relative-001 | += | +Ahem | +CSS Regions: flowing content that has position: relative
+
|
+
+ regions-transforms-008 | += | +Ahem | +CSS Regions: Transformed named flow (text) content that breaks across multiple regions and overflows
+
|
+
+ regions-transforms-009 | += | +Ahem | +CSS Regions: Transformed region with named flow (text) content that breaks across multiple regions and overflows
+
|
+
+ regions-transforms-013 | += = | ++ | CSS Regions: Transformed named flow (monolithic) content that breaks across multiple regions
+
|
+
+ regions-transforms-020 | += | ++ | CSS Regions: Transformed region with named flow (fragmentable) content that breaks across multiple regions
+
|
+
+ regions-transforms-021 | += | ++ | CSS Regions: Transforms on multiple named flow (non-text) content nodes that break across multiple regions
+
|
+
+ regions-transforms-022 | += | +Ahem | +CSS Regions: Transforms on multiple named flow (text) content nodes that break across multiple regions
+
|
+
Test | +Refs | +Flags | +Info | +
---|---|---|---|
+ + + 6 Conformance | |||
+ + + 6.1 Document Conventions | |||
+ + + 6.2 Conformance Classes | |||
+ + + 6.3 Partial Implementations | |||
+ + + 6.4 Experimental Implementations | |||
+ + + 6.5 Non-Experimental Implementations | |||
+ + + 6.6 CR Exit Criteria |
+ Test passes if you see two squares separated by a small vertical space. The squares should
+ have a black outline, the top square should be blue and the bottom one should be green.
+ You should see no red.
+
+
+
+
+ Test passes if you see two identical rows of colored squares. Each row should have three
+ squares, from left to right as follows: blue, gray, green. The squares in a row should
+ be flush to each other, but the two rows should have some space between them.
+ Test fails is you see any red.
+
+
+
+ + Test passes if you see two colored squares each inside a black-bordered rectangle: +
+
+
+
+ + Test passes if you see two colored squares each inside a black-bordered rectangle: +
+
+
+
Test passes if you see two green squares (one bigger and one smaller) and no red.
++
+
+ Test passes if you see two squares separated by a small vertical space. The squares should
+ have a black outline, the top square should be blue and the bottom one should be green.
+ You should see no red.
+
+ Test passes if you see two identical rows of colored squares. Each row should have three
+ squares, from left to right as follows: blue, gray, green. The squares in a row should
+ be flush to each other, but the two rows should have some space between them.
+ Test fails is you see any red.
+
+ + Test passes if you see two colored squares each inside a black-bordered rectangle: +
+ + Test passes if you see two colored squares each inside a black-bordered rectangle: +
Test passes if you see two green squares (one bigger and one smaller) and no red.
+The test passes if:
+The test passes if you see either two green squares or one vertical green rectangle. There should be no red.
+ + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/xhtml1print/reference/regions-transforms-013-ref.xht b/tests/wpt/css-tests/css-break-3_dev/xhtml1print/reference/regions-transforms-013-ref.xht new file mode 100644 index 00000000000..5a6a3049a08 --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/xhtml1print/reference/regions-transforms-013-ref.xht @@ -0,0 +1,21 @@ + + +The test passes if you see either two green squares or one vertical green rectangle. There should be no red.
+ + + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/xhtml1print/reference/regions-transforms-020-ref.xht b/tests/wpt/css-tests/css-break-3_dev/xhtml1print/reference/regions-transforms-020-ref.xht new file mode 100644 index 00000000000..aae13775fd8 --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/xhtml1print/reference/regions-transforms-020-ref.xht @@ -0,0 +1,21 @@ + + +The test passes if you see two green squares and no red.
+ + + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/xhtml1print/reftest-toc.xht b/tests/wpt/css-tests/css-break-3_dev/xhtml1print/reftest-toc.xht new file mode 100644 index 00000000000..48d26f46228 --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/xhtml1print/reftest-toc.xht @@ -0,0 +1,121 @@ + + + + + +Test | +Reference | +Flags | +
---|---|---|
+ floats-clear-breaks-002 | += | +Ahem | +
+ floats-in-named-flow-012 | += | +Ahem | +
+ floats-in-named-flow-029 | += | +Ahem | +
+ floats-in-named-flow-030 | += | +Ahem | +
+ position-relative-001 | += | +Ahem | +
+ regions-transforms-008 | += | +Ahem | +
+ regions-transforms-009 | += | +Ahem | +
+ regions-transforms-013 | += | ++ |
= | +||
+ regions-transforms-020 | += | ++ |
+ regions-transforms-021 | += | ++ |
+ regions-transforms-022 | += | +Ahem | +
The test passes if:
+The test passes if:
+The test passes if you see either two green squares or one vertical green rectangle. There should be no red.
+ + + + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/xhtml1print/regions-transforms-020.xht b/tests/wpt/css-tests/css-break-3_dev/xhtml1print/regions-transforms-020.xht new file mode 100644 index 00000000000..e0866521167 --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/xhtml1print/regions-transforms-020.xht @@ -0,0 +1,61 @@ + + + +The test passes if you see two green squares and no red.
+ + +The test passes if you see two green squares and no red.
+ + + + + + \ No newline at end of file diff --git a/tests/wpt/css-tests/css-break-3_dev/xhtml1print/regions-transforms-022.xht b/tests/wpt/css-tests/css-break-3_dev/xhtml1print/regions-transforms-022.xht new file mode 100644 index 00000000000..0836a17cd7d --- /dev/null +++ b/tests/wpt/css-tests/css-break-3_dev/xhtml1print/regions-transforms-022.xht @@ -0,0 +1,83 @@ + + + +The test passes if you see two green squares and no red.
+This index contains both + self-describing tests + and reftests. + A separate alphabetical reftest index + is provided for tests in reftest + format along with the reftest manifest.
+ +Chapter 1 - + Introduction | +(0 Tests) |
---|---|
Chapter 2 - + Fragmentation Model and Terminology | +(4 Tests) |
Chapter 3 - + Controlling Breaks | +(0 Tests) |
Chapter 4 - + Rules for Breaking | +(2 Tests) |
Chapter 5 - + Box Model for Breaking | +(9 Tests) |
Chapter 6 - + Conformance | +(0 Tests) |