samples/tests/samples/lib/layout/layout_test.dart - Issue 15755017: Switch from DRT to content shell.

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

Unified Diff: samples/tests/samples/lib/layout/layout_test.dart

Issue 15755017: Switch from DRT to content shell. (Closed) Base URL: https://dart.googlecode.com/svn/branches/bleeding_edge/dart

Patch Set: Created 7 years, 7 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:

Index: samples/tests/samples/lib/layout/layout_test.dart

diff --git a/samples/tests/samples/lib/layout/layout_test.dart b/samples/tests/samples/lib/layout/layout_test.dart

index 38d1089f01b0815687002c8bfffd9bf3e6fdbdb2..f49408ce0e0da735a43ba728de6310080b6ce0ac 100644

--- a/samples/tests/samples/lib/layout/layout_test.dart

+++ b/samples/tests/samples/lib/layout/layout_test.dart

@@ -19,7 +19,7 @@ part 'grid_examples.dart';

part 'css.dart';

// TODO(jmesserly): these tests would be easier to work with if they were WebKit

-// layout tests. The way DumpRenderTree works is exactly what we want for

+// layout tests. The way content shell works is exactly what we want for

// testing layout: run the example and then print the element tree with metrics.

// The UnitTestSuite wrapper gets in our way here, because you can't "see" the

// test layout visually when you're debugging.