third_party/WebKit/LayoutTests/http/tests/streams/byte-length-queuing-strategy.html - Issue 1378213002: Implement ByteLengthQueuingStrategy

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/streams/byte-length-queuing-strategy.html

Issue 1378213002: Implement ByteLengthQueuingStrategy (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

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

OLD	NEW
(Empty)
	1 <!DOCTYPE html>

	2 <meta charset="utf-8">

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

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

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

	6

	7 <script src="byte-length-queuing-strategy.js"></script>

	8 <script>

	9 'use strict';

	10 fetch_tests_from_worker(new Worker('byte-length-queuing-strategy.js'));

	11 fetch_tests_from_worker(new SharedWorker('byte-length-queuing-strategy.js'));

	12 service_worker_test('byte-length-queuing-strategy.js');
	tyoshino (SeeGerritForStatus) 2015/10/02 11:33:28 So, this test is run with HTTP server (placed in h So, this test is run with HTTP server (placed in http/tests/...) since we want to check that it works under ServiceWorker environment? domenic 2015/10/02 22:32:14 Yes. I followed the pattern from the promise rejec Show quoted text On 2015/10/02 at 11:33:28, tyoshino wrote: > So, this test is run with HTTP server (placed in http/tests/...) since we want to check that it works under ServiceWorker environment? Yes. I followed the pattern from the promise rejection event tests which are another cross-environment feature.
	13 </script>

OLD	NEW