LayoutTests/compositing/will-change/gpu-rasterization-hint-added.html - Issue 233063004: Suppress layer creation for descendants of GPU-rasterized layers

Side by Side Diff

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

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: LayoutTests/compositing/will-change/gpu-rasterization-hint-added.html

Issue 233063004: Suppress layer creation for descendants of GPU-rasterized layers (Closed) Base URL: svn://svn.chromium.org/blink/trunk

Patch Set: Rebased Created 6 years, 8 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 unified diff | Download patch | Annotate | Revision Log

« no previous file with comments | « no previous file | LayoutTests/compositing/will-change/gpu-rasterization-hint-added-expected.txt » ('j') | LayoutTests/compositing/will-change/gpu-rasterization-hint-removed.html » ('J')
Toggle Intra-line Diffs ('i') | Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

OLD	NEW
(Empty)
	1 <!DOCTYPE html>

	2 <html>

	3 <head>

	4 <style>

	5 #container {

	6 will-change: top;

	7 position: absolute;

	8 z-index: 0;

	9 left: 200px;

	10 top: 100px;

	11 width: 100px;

	12 height: 100px;

	13 background-color: blue;

	14 }

	15

	16 #willChangeOpacity {

	17 position: absolute;

	18 left: 50px;

	19 top: 50px;

	20 width: 75px;

	21 height: 75px;

	22 background-color: green;

	23 will-change: opacity;

	24 }

	25 </style>

	26 <script type="text/javascript">

	27 if (window.internals) {

	28 window.internals.settings.setAcceleratedCompositingForGpuRasterizationHint Enabled(true);

	29 // Force an update of the compositing triggers.

	30 window.internals.forceCompositingUpdate(document);

	31 }

	32

	33 function doTest()

	34 {

	35 if (window.internals) {

	36 window.internals.forceCompositingUpdate(document);

	37 }
	abarth-chromium 2014/04/14 20:25:53 Why do we need to force a compositing update here? Why do we need to force a compositing update here? ajuma 2014/04/15 19:11:34 This is to ensure that we've updated compositing w Show quoted text On 2014/04/14 20:25:53, abarth wrote: > Why do we need to force a compositing update here? This is to ensure that we've updated compositing with the old value of will-change before we set its new value (since otherwise, this test wouldn't really be testing that we get correct behavior when will-change changes (from "top" to "contents"), it would only be testing the behavior for the new value of will-change ("contents").
	38 // Adding "will-change: contents" to the container div should

	39 // stop its child from compositing.

	40 document.getElementById("container").style.willChange = "contents";

	41 if (window.testRunner) {

	42 document.getElementById("layertree").innerText = window.internals.layerT reeAsText(document);

	43 testRunner.dumpAsText();

	44 }

	45 }

	46

	47 window.addEventListener('load', doTest, false);

	48 </script>

	49 </head>

	50

	51 <body>

	52 <div id="container">

	53 <div id="willChangeOpacity"></div>

	54 </div>

	55

	56 <pre id="layertree"></pre>

	57 </body>

	58

	59 </html>

OLD	NEW