Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(53)

Side by Side Diff: third_party/WebKit/LayoutTests/custom-elements/imports/async-imports.html

Issue 2242743002: Make custom elements work in HTML imports (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: update test 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:
View unified diff | Download patch
OLDNEW
(Empty)
1 <!DOCTYPE html>
2 <script src="../../resources/testharness.js"></script>
3 <script src="../../resources/testharnessreport.js"></script>
4 <link rel="import" href="resources/async-component.html" async>
5 <async-component></async-component>
6 <script>
7 'use strict';
8 promise_test(() => {
9 return customElements.whenDefined('async-component').then(() => {
10 let el = document.querySelector('async-component');
dominicc (has gone to gerrit) 2016/08/22 01:46:36 'el' is kind of neither here nor there; the name c
kochi 2016/08/22 07:37:34 Done.
11 assert_true(el instanceof AsyncComponent,
dominicc (has gone to gerrit) 2016/08/22 01:46:36 In a lot of tests we assert something has been upg
kochi 2016/08/22 07:37:34 Done.
12 '<async-component> in this document should have been upgraded.') ;
13
14 let link = document.querySelector('link[rel=import]');
15 let elInImport = link.import.querySelector('async-component');
16 assert_true(elInImport instanceof AsyncComponent,
17 '<async-component> in imported document should have been upgrade d.');
18 });
19 }, 'Custom Elements definition in async import should work.');
20 </script>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698