Commit 5ba94fcf authored by Julie Jeongeun Kim's avatar Julie Jeongeun Kim Committed by Commit Bot

[css-flexbox] Move max-width-violation.html from css3/flexbox to WPT

This CL migrates this test out of
third_party/blink/web_tests/css3/flexbox and into the WPT-specific
directory, adding links to the relevant specs and a test assertion
describing its purpose.

Bug: 1063749
Change-Id: I9e3ce8c44ad2ca7852aeae25e99d4ebbf6c959f3
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2124130
Commit-Queue: Julie Kim <jkim@igalia.com>
Reviewed-by: default avatarRobert Ma <robertma@chromium.org>
Reviewed-by: default avatarChristian Biesinger <cbiesinger@chromium.org>
Cr-Commit-Position: refs/heads/master@{#754393}
parent 9adde391
<!DOCTYPE html>
<title>CSS Flexbox: max-width of inflexible items</title>
<link rel="help" href="https://drafts.csswg.org/css-flexbox/#resolve-flexible-lengths">
<link rel="help" href="https://drafts.csswg.org/css-flexbox/#flexibility">
<link rel="bookmark" href="https://crbug.com/617956">
<meta name="assert" content="Inflexible items (flex factor 0 or flex basis violating the min/max size constraint) take max-width into account.">
<style>
.columns {
display: flex;
......@@ -33,16 +37,14 @@
}
</style>
<script src="../../resources/testharness.js"></script>
<script src="../../resources/testharnessreport.js"></script>
<script src="../../resources/check-layout-th.js"></script>
<script src="/resources/testharness.js"></script>
<script src="/resources/testharnessreport.js"></script>
<script src="/resources/check-layout-th.js"></script>
<body onload="checkLayout('.columns')">
<div id=log></div>
<p>You should see no red</p>
<div class="columns">
<div class="red"></div>
<div class="column1" data-expected-width="150">
......@@ -54,7 +56,6 @@
</div>
<p>This second part is just to ensure we don't assert</p>
<div class="columns">
<div class="column1 abspos" data-expected-width="150">
Column 1
......@@ -63,4 +64,3 @@
Column 2
</div>
</div>
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment