summaryrefslogtreecommitdiffstats
path: root/testing/web-platform/tests/css/CSS2/floats/floats-wrap-bfc-with-margin-001-ref.html
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-19 00:47:55 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-19 00:47:55 +0000
commit26a029d407be480d791972afb5975cf62c9360a6 (patch)
treef435a8308119effd964b339f76abb83a57c29483 /testing/web-platform/tests/css/CSS2/floats/floats-wrap-bfc-with-margin-001-ref.html
parentInitial commit. (diff)
downloadfirefox-26a029d407be480d791972afb5975cf62c9360a6.tar.xz
firefox-26a029d407be480d791972afb5975cf62c9360a6.zip
Adding upstream version 124.0.1.upstream/124.0.1
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'testing/web-platform/tests/css/CSS2/floats/floats-wrap-bfc-with-margin-001-ref.html')
-rw-r--r--testing/web-platform/tests/css/CSS2/floats/floats-wrap-bfc-with-margin-001-ref.html121
1 files changed, 121 insertions, 0 deletions
diff --git a/testing/web-platform/tests/css/CSS2/floats/floats-wrap-bfc-with-margin-001-ref.html b/testing/web-platform/tests/css/CSS2/floats/floats-wrap-bfc-with-margin-001-ref.html
new file mode 100644
index 0000000000..8e079b1f17
--- /dev/null
+++ b/testing/web-platform/tests/css/CSS2/floats/floats-wrap-bfc-with-margin-001-ref.html
@@ -0,0 +1,121 @@
+<!DOCTYPE html>
+<html class="reftest-wait">
+<meta charset="utf-8">
+<title>CSS Reference Case</title>
+<link rel="author" title="Daniel Holbert" href="mailto:dholbert@mozilla.com">
+<script>
+ const MARGIN_VALS = [-30, -20, -17,
+ // Values -16 through -1 are non-interoperable and are
+ // split off to a separate test.
+ 0, 5, 10, 14
+ // Values over 15 are non-interoperable and are
+ // split off to a separate test.
+ ];
+ const HORIZ_SIDES = ["left", "right"]; // Used for 'float:*' and 'margin-*'.
+ const DIRECTION_VALS = ["ltr", "rtl"];
+
+ function newDivWithClassAndParent(className, parent) {
+ let elem = document.createElement("div");
+ if (className) {
+ elem.classList.add(className);
+ }
+ parent.appendChild(elem);
+ return elem;
+ }
+ function generateGroup(directionVal, floatVal, marginPropSuffix) {
+ let group = newDivWithClassAndParent("group", document.body);
+ group.style.direction = directionVal;
+ const marginPropName = "margin-" + marginPropSuffix;
+
+ for (let v of MARGIN_VALS) {
+ // In this test, the negative values are specifically the ones that
+ // are expected to cause wrapping.
+ const isExpectingToWrap = (v < 0);
+ let container = newDivWithClassAndParent("container", group);
+ if (isExpectingToWrap) {
+ container.style.flexWrap = "wrap";
+ }
+ if ((floatVal == "right") != (directionVal == "rtl")) {
+ // In the corresponding piece of the testcase, the float is floated to
+ // the inline-end side (for the given writing-mode). We use a
+ // "row-reverse" flex container as our mockup for that here.
+ container.style.flexDirection = "row-reverse";
+ }
+
+ let float = newDivWithClassAndParent("float", container);
+ float.style.cssFloat = floatVal;
+
+ let bfc = newDivWithClassAndParent("bfc", container);
+ if (isExpectingToWrap) {
+ // If we wrap, then we expect the testcase to resolve the BFC's
+ // content-box width to be: 30px (container's available space)
+ // minus 2px (for bfc's border), plus the absolute value of whatever
+ // (negative) margin value we're testing here.
+ bfc.style.width = (30 - 2 - v) + "px";
+ }
+
+ // Set the actual margin value that we're testing here, EXCEPT if we're
+ // not-expecting-to-wrap and the bfc's margin is going to "overlap" the
+ // float in the testcase. (In this latter case, the margin doesn't
+ // impact the testcase's rendering, so we take care not to set it here.)
+ if (isExpectingToWrap || marginPropSuffix != floatVal) {
+ bfc.style[marginPropName] = v + "px";
+ }
+ }
+ }
+ function go() {
+ for (let directionVal of DIRECTION_VALS) {
+ for (let floatVal of HORIZ_SIDES) {
+ for (let marginPropSuffix of HORIZ_SIDES) {
+ generateGroup(directionVal, floatVal, marginPropSuffix);
+ }
+ }
+ }
+ // Note: the "reftest-wait" usage here isn't strictly necessary; it just
+ // helps ensure that we actually make it through all of the above JS and
+ // populate this document with the content that we want to render.
+ // (Specifically: if we e.g. throw a JS exception somewhere early in both
+ // the testcase and reference case, then the "reftest-wait" class will
+ // never be removed; and that will cause the test run to be classified
+ // as a failure, rather than a trivial "pass" with a visual comparison of
+ // two blank documents.)
+ document.documentElement.removeAttribute("class");
+ }
+</script>
+<style>
+.group {
+ width: 500px;
+ border: 1px solid black;
+}
+.container {
+ display: inline-flex;
+ align-content: start;
+ vertical-align: top;
+ width: 30px;
+ height: 40px;
+ /* This border and margin are just cosmetic, to avoid overlap between
+ * adjacent containers within a row. */
+ border: 1px solid gray;
+ margin-left: 30px;
+}
+
+.float {
+ width: 7px;
+ height: 8px;
+ background: fuchsia;
+ border: 1px solid purple;
+ margin: 1px 3px 1px 2px;
+}
+.bfc {
+ display: flow-root;
+ background: aqua;
+ height: 15px;
+ border: 1px solid blue;
+ /* We use "flex: 1" (on a flex item) to mock up the fill-available-space
+ * block-layout behavior in the testcase. */
+ flex: 1 auto;
+}
+</style>
+<body onload="go()">
+</body>
+</html>