third_party/WebKit/LayoutTests/custom-elements/imports/parser-customize-imports.html - Issue 2242743002: Make custom elements work in HTML imports

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/custom-elements/imports/parser-customize-imports.html

Issue 2242743002: Make custom elements work in HTML imports (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: rebase wip Created 4 years, 4 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 <script src="../../resources/testharness.js"></script>

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

	4 <script>

	5 let constructors = [];

	6 </script>

	7

	8 <link rel="import" href="resources/parser-customize.html">
	dominicc (has gone to gerrit) 2016/08/19 04:54:11 So... this blocks script, not parsing. Why can you So... this blocks script, not parsing. Why can you rely on the order these are upgraded in? kochi 2016/08/19 10:51:48 Talked offline, this was based on my misunderstand Show quoted text On 2016/08/19 04:54:11, dominicc wrote: > So... this blocks script, not parsing. Why can you rely on the order these are > upgraded in? Talked offline, this was based on my misunderstanding about where the parsing is blocked.
	9

	10 <parser-customize></parser-customize>

	11

	12 <script>

	13 test(() => {

	14 assert_equals(constructors.length, 3);

	15 assert_equals(constructors[0], 'parser-customize');

	16 assert_equals(constructors[1], 'parser-customize');

	17 assert_equals(constructors[2], 'parser-customize');

	18 }, 'Parser should customize and synchronously call the constructor.');

	19 </script>

OLD	NEW