third_party/WebKit/LayoutTests/http/tests/performance-timing/paint-timing/basetest.html - Issue 2932593002: Attempt 2: Update PaintTiming Web Perf APIs for FP & FCP to report swap time

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: third_party/WebKit/LayoutTests/http/tests/performance-timing/paint-timing/basetest.html

Issue 2932593002: Attempt 2: Update PaintTiming Web Perf APIs for FP & FCP to report swap time (Closed)

Patch Set: Add two more tests Created 3 years, 6 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

OLD	NEW
(Empty)
	1 <!DOCTYPE html>

	2 <head>

	3 <title>Performance Paint Timing Test</title>

	4 </head>

	5 <body>

	6 <script src="../../resources/testharness.js"></script>

	7 <script src="../../resources/testharnessreport.js"></script>

	8 <div id="main"></div>

	9

	10 <script>

	11 async_test(function(t) {

	12 testRunner.capturePixelsAsyncThen(t.step_func(function() {

	13 bufferedEntries = performance.getEntriesByType('paint');

	14 assert_equals(bufferedEntries.length, 0, "No paint entries yet");

	15

	16 var div = document.createElement("div");
	tdresser 2017/06/09 14:26:27 Should we use const/let in tests at this point? Should we use const/let in tests at this point? panicker 2017/06/09 20:29:48 Done. Show quoted text On 2017/06/09 14:26:27, tdresser wrote: > Should we use const/let in tests at this point? Done.
	17 div.style.width = "100px";

	18 div.style.height = "100px";

	19 div.style.backgroundColor = "red";

	20 div.style.color = "blue";

	21 div.innerHTML = "test"

	22 document.getElementById("main").appendChild(div);

	23

	24 testRunner.capturePixelsAsyncThen(t.step_func_done(function() {

	25 bufferedEntries = performance.getEntriesByType('paint');

	26 assert_equals(bufferedEntries.length, 2, "FP and FCP.");

	27 assert_equals(bufferedEntries[0].entryType, "paint");

	28 assert_equals(bufferedEntries[0].name, "first-paint");

	29 assert_equals(bufferedEntries[1].entryType, "paint");

	30 assert_equals(bufferedEntries[1].name, "first-contentful-paint") ;

	31 }));

	32 }));

	33 }, "Basic test to check existence of FP and FCP.");

	34 </script>

	35 </body>

	36 </html>

OLD	NEW