[@container] Always create ContainerQueryEvaluator on demand

lilles · chromium-wpt-export-bot · commit 30a0ef9643fb · 2023-06-01T02:07:55.000-07:00
Creating them eagerly for size containers and lazily for style containers made the code confusing and hard to reason about. Also there was a bug with incorrect evaluation of style queries for size containers with unknown results for it size features. That is fixed by making sure we do not create ContainerQueryEvaluators without a MediaQueryEvaluator. Bug: 1450054 Change-Id: I9af679badaff645da3d2b20a816821a7d1b266f5 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4567559 Reviewed-by: Anders Hartvoll Ruud <andruud@chromium.org> Commit-Queue: Rune Lillesveen <futhark@chromium.org> Cr-Commit-Position: refs/heads/main@{#1151733}
diff --git a/css/css-contain/container-queries/style-query-with-unknown-width.html b/css/css-contain/container-queries/style-query-with-unknown-width.html
@@ -0,0 +1,26 @@
+<!DOCTYPE html>
+<title>CSS Container Queries Test: style and size query against container without a principal box</title>
+<link rel="help" href="https://drafts.csswg.org/css-contain-3/#container-queries">
+<script src="/resources/testharness.js"></script>
+<script src="/resources/testharnessreport.js"></script>
+<script src="support/cq-testcommon.js"></script>
+<style>
+  #container {
+    container-type: inline-size;
+    display: contents;
+    --foo: bar;
+  }
+  @container (width >= 0px) or style(--foo: bar) {
+    #target { color: green; }
+  }
+</style>
+<div id="container">
+  <div id="target">Should be green</div>
+</div>
+<script>
+  setup(() => assert_implements_container_queries());
+
+  test(() => {
+    assert_equals(getComputedStyle(target).color, "rgb(0, 128, 0)");
+  }, "width query should evaluate to unknown and style query to true");
+</script>
