summaryrefslogtreecommitdiffstats
path: root/packages/meshbay-hub/tests/test_layout_responsive.py
diff options
context:
space:
mode:
Diffstat (limited to 'packages/meshbay-hub/tests/test_layout_responsive.py')
-rw-r--r--packages/meshbay-hub/tests/test_layout_responsive.py12
1 files changed, 9 insertions, 3 deletions
diff --git a/packages/meshbay-hub/tests/test_layout_responsive.py b/packages/meshbay-hub/tests/test_layout_responsive.py
index 741e728..0e2444c 100644
--- a/packages/meshbay-hub/tests/test_layout_responsive.py
+++ b/packages/meshbay-hub/tests/test_layout_responsive.py
@@ -12,9 +12,15 @@ for 440 px:
`margin-left: auto` pushed the excess off the right-hand side rather than the
left — which is exactly how it was seen.
-These assertions read the stylesheet. That is weak evidence and it is what is
-available: there is no browser in this suite, so a layout cannot be measured
-here, only its inputs pinned. What they buy is that the four rules holding the
+These assertions read the stylesheet, which pins the inputs to a layout without
+measuring the layout. That was all there was when they were written; it is no
+longer. `test_layout_measured.py` renders the real stylesheet in Chrome at a
+phone width and asserts on rectangles, which is what caught the transfers panel
+hanging 138 px off the left of a 320 px screen — a defect no reading of
+`width: 330px` would have revealed, since it came from where the panel was
+anchored rather than from how wide it was.
+
+Prefer that for anything new. What these buy is that the four rules holding the
toolbar together cannot be removed without something saying so.
"""