LayoutTests/fast/regions/region-styling/render-region-custom-style-mark.html - Issue 159933010: Remove everything region-specific from LayoutTests.

Unified Diff: LayoutTests/fast/regions/region-styling/render-region-custom-style-mark.html

Issue 159933010: Remove everything region-specific from LayoutTests. (Closed) Base URL: https://chromium.googlesource.com/chromium/blink.git@master

Patch Set: Created 6 years, 10 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« no previous file with comments | « LayoutTests/fast/regions/region-styling/removed-element-style-in-region-crash-expected.txt ('k') | LayoutTests/fast/regions/region-styling/render-region-custom-style-mark-expected.html » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/fast/regions/region-styling/render-region-custom-style-mark.html

diff --git a/LayoutTests/fast/regions/region-styling/render-region-custom-style-mark.html b/LayoutTests/fast/regions/region-styling/render-region-custom-style-mark.html

deleted file mode 100644

index 92b1699e3d9713bd3b8390f497638eff124cff2b..0000000000000000000000000000000000000000

--- a/LayoutTests/fast/regions/region-styling/render-region-custom-style-mark.html

+++ /dev/null

@@ -1,62 +0,0 @@

-<!doctype html>

-<html>

- <!--

- Tests that regions with region styling rules associated are identified and flagged correctly.

- When an element is no longer a region, the region styling should not apply anymore.

- When an element becomes a region, region styling should be applied.

- You should not see any red background below.

- -->

- <head>

- <style>

- @font-face {

- font-family: webkit-ahem;

- font-style: normal;

- src: url(../../../resources/Ahem.ttf);

- }

- p { font-family: webkit-ahem; }

- #p1 { -webkit-flow-into: flow1; background-color: red; }

- .region1 { -webkit-flow-from: flow1; }

- #region1 { position: absolute; top: 10px; width: 300px; height: 50px; }

- @-webkit-region #region1 { #p1 { background-color: green; } }

- #p2 { -webkit-flow-into: flow2; background-color: red; }

- .region2 { -webkit-flow-from: flow2; }

- #region2 { position: absolute; top: 70px; width: 300px; height: 50px; }

- @-webkit-region #region2 { #p2 { background-color: green; } }

- #containerP3 { position: absolute; top: 130px; width: 300px; height: 50px; }

- #p3 { -webkit-flow-into: flow3; background-color: green; }

- .region3 { -webkit-flow-from: flow3; }

- #region3 { position: absolute; top: 130px; width: 300px; height: 50px; }

- @-webkit-region #region3 { #p3 { background-color: red; } }

- #region4 { position: absolute; top: 190px; width: 300px; height: 50px; }

- </style>

- </head>

- <body>

-

- <p id="p1">R: 00 G: 80 B: 00</p>

- <!-- Paragraph collected into a named flow. When we dynamically add a region to collect the flow,

- region styling rule is applied. -->

- <p id="p2">R: 00 G: 80 B: 00</p>

- <!-- Paragraph flown into a region with region styling. The region element is transformed

- so that the element is not a region, region styling rule should not apply. -->

- <p id="p3" class="p3">R: 00 G: 80 B: 00</p>

- <div id="region1" class="region1"></div>

- <div id="region2"></div>

- <div id="region3" class="region3"></div>

- <div id="region4" class="region3"</div>

- <script>

- // When the element becomes a region, the region styling should be applied.

- document.getElementById("region2").className = "region2";

- // When the element is no longer a region, the region styling should not apply anymore.

- document.getElementById("region3").className = "";

- </script>

- </body>

-</html>