forked from mirrors/gecko-dev
b6e2c8b912
Automatic update from web-platform-tests [css-flex] Move moz flex tests from vendor-imports to css/css-flexbox Updated TestExpectations in place and organized the flex section a bit. 7 tests weren't moved because I already ported those to check-layout versions in css/css-flexbox and they hadn't been deleted from vendor-imports yet. Removed two tests from css3/flexbox/mozilla because they were in the move. One test is still in that directory because it wasn't in vendor-imports. Change-Id: I15e815ea15e30eee4568c65aa92dd364c17a5e9e Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2585929 Commit-Queue: Philip Jägenstedt <foolip@chromium.org> Reviewed-by: Philip Jägenstedt <foolip@chromium.org> Cr-Commit-Position: refs/heads/master@{#836059} -- Suppress new lint errors after moving flexbox tests -- wpt-commits: f5cc59806ce585bfdff8ac775de12b18e22a4ef0, d882d1829205f38d8b2ffff2ccd11c9cd24a0d05 wpt-pr: 26848
79 lines
2.5 KiB
HTML
79 lines
2.5 KiB
HTML
<!DOCTYPE html>
|
|
<!--
|
|
Any copyright is dedicated to the Public Domain.
|
|
http://creativecommons.org/publicdomain/zero/1.0/
|
|
-->
|
|
<!-- Testcase to ensure we handle ::before and ::after pseudo-elements on
|
|
a flex container and treat them as flex items (e.g. honoring "order").
|
|
-->
|
|
<html>
|
|
<head>
|
|
<title>CSS Test: Testing that generated content nodes are treated as a flex items, and honor 'order'</title>
|
|
<link rel="author" title="Daniel Holbert" href="mailto:dholbert@mozilla.com">
|
|
<link rel="help" href="http://www.w3.org/TR/css-flexbox-1/#flex-items">
|
|
<link rel="match" href="flexbox-with-pseudo-elements-002-ref.html">
|
|
<meta charset="utf-8">
|
|
<style>
|
|
.flexContainer {
|
|
display: flex;
|
|
margin-bottom: 2px;
|
|
background: lightgray;
|
|
}
|
|
.withBefore::before {
|
|
content: 'b';
|
|
background: yellow;
|
|
/* This 'order' value should place us after the other elements, visually,
|
|
even though we're ::before. */
|
|
order: 1;
|
|
}
|
|
.withAfter::after {
|
|
content: 'a';
|
|
background: lightblue;
|
|
/* This 'order' value should place us before the other elements, visually,
|
|
even though we're ::after. */
|
|
order: -1;
|
|
}
|
|
</style>
|
|
</head>
|
|
<body>
|
|
<!-- 'b' should be at end, due to its high 'order' value: -->
|
|
<div class="flexContainer withBefore">
|
|
<div>I</div>
|
|
</div>
|
|
|
|
<!-- 'b' should be at beginning, since it's '::before' and the other item has
|
|
a matching 'order' value: -->
|
|
<div class="flexContainer withBefore">
|
|
<div style="order: 1">I</div>
|
|
</div>
|
|
|
|
<!-- 'a' should be at beginning, due to its low 'order' value: -->
|
|
<div class="flexContainer withAfter">
|
|
<div>I</div>
|
|
</div>
|
|
|
|
<!-- 'b' should be at beginning, since it's '::after' and the other item has
|
|
a matching 'order' value: -->
|
|
<div class="flexContainer withAfter">
|
|
<div style="order: -1">I</div>
|
|
</div>
|
|
|
|
<!-- As above, the ::after 'a' should be at beginning, and the ::before 'b'
|
|
should be at end, due to their 'order' values -->
|
|
<div class="flexContainer withBefore withAfter">
|
|
<div>I</div>
|
|
</div>
|
|
|
|
<!-- ...but now the normal item "I" has its order increased, so it'll go
|
|
at the end. -->
|
|
<div class="flexContainer withBefore withAfter">
|
|
<div style="order: 1">I</div>
|
|
</div>
|
|
|
|
<!-- ...and now the normal item "I" has its order reduced, so it'll go
|
|
at the beginning. -->
|
|
<div class="flexContainer withBefore withAfter">
|
|
<div style="order: -1">I</div>
|
|
</div>
|
|
</body>
|
|
</html>
|