LayoutTests/fast/regions/region-leak-js-information-when-disabled-at-runtime.html - Issue 159863002: Remove CSS regions support, keeping a bare minimum to support "region-based" multicol.

Unified Diff: LayoutTests/fast/regions/region-leak-js-information-when-disabled-at-runtime.html

Issue 159863002: Remove CSS regions support, keeping a bare minimum to support "region-based" multicol. (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-height-defined-to-auto-expected.txt ('k') | LayoutTests/fast/regions/region-leak-js-information-when-disabled-at-runtime-expected.txt » ('j') | Source/devtools/front_end/protocol_externs.js » ('J')
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: LayoutTests/fast/regions/region-leak-js-information-when-disabled-at-runtime.html

diff --git a/LayoutTests/fast/regions/region-leak-js-information-when-disabled-at-runtime.html b/LayoutTests/fast/regions/region-leak-js-information-when-disabled-at-runtime.html

deleted file mode 100644

index a843372920c3c28c94320e33f1dbc5e5a3fd4de4..0000000000000000000000000000000000000000

--- a/LayoutTests/fast/regions/region-leak-js-information-when-disabled-at-runtime.html

+++ /dev/null

@@ -1,40 +0,0 @@

-<!doctype html>

-<html>

- <!--

- The bug is that the CSS Regions feature leaks information at run-time. There are JS properties that exist even

- if the feature is disabled at run-time (document.webkitGetNamedFlows, document.body.webkitRegionOverset,

- document.body.webkitGetRegionFlowRanges and window.WebKitCSSRegionRule).

- The best LayoutTest would test that the properties exist when the feature is enabled and that the properties

- just aren't there when the feature is disabled.

- But, since during running Layout Tests the feature is enabled by default and switching the

- RuntimeEnabledFeatures requires the process to be restarted and that is currently not possible, we can only test

- that the properties exist and have the proper type.

- On success, you should see a series of PASS messages.

- -->

- <head>

- <script src="../../resources/js-test.js"></script>

- </head>

- <body>

- <script>

- description("<p>Test for <a href=\"https://bugs.webkit.org/show_bug.cgi?id=94070\">94070 [CSSRegions] broken feature detection: syntax parsing succeeds when CSS REGIONS is disabled at runtime</a></p>");

- shouldBeEqualToString( "typeof(document.webkitGetNamedFlows)", "function" );

- shouldBeEqualToString( "typeof(document.body.webkitRegionOverset)", "string" );

- shouldBeEqualToString( "typeof(document.body.webkitGetRegionFlowRanges)", "function" );

- shouldBeDefined( "window.WebKitCSSRegionRule" );

-/*

- // FIXME: uncomment the following code when switching a RuntimeEnabledFeatures flag doesn't require the browser

- // process to be restarted.

- if(window.testRunner)

- window.testRunner.overridePreference("WebKitCSSRegionsEnabled", false);

- shouldBeFalse( "'webkitGetNamedFlows' in document" );

- shouldBeFalse( "document.body.hasOwnProperty( 'webkitRegionOverset' )" );

- shouldBeFalse( "'webkitGetRegionFlowRanges' in document.body" );

- shouldBeUndefined( "window.WebKitCSSRegionRule" );

-*/

- </script>

- </body>

-</html>