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

Side by Side Diff: LayoutTests/fast/dom/custom/document-register-on-create-callback.html

Issue 106903007: Let unresolved custom element go through CustomElementCallbackQueue. (Closed) Base URL: svn://svn.chromium.org/blink/trunk
Patch Set: Updated Created 7 years 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 | Annotate | Revision Log
OLDNEW
(Empty)
1 <!DOCTYPE html>
2 <script src="../../../resources/js-test.js"></script>
dominicc (has gone to gerrit) 2013/12/14 02:42:39 I want to know more about your concern re: timing.
Hajime Morrita 2013/12/16 09:00:34 It's tricky to interleave <script> elements and ot
dominicc (has gone to gerrit) 2013/12/18 08:46:41 Can't you use async_test?
3 <script>
4 description("document.register() in a createdCallback should upgrade elements th at are in the same processing queue.");
5
6 var createdElements = [];
7
8 var protoA = Object.create(HTMLElement.prototype);
9 protoA.createdCallback = function () {
10 createdElements.push(this.id);
11 var protoB = Object.create(HTMLElement.prototype);
12 protoB.createdCallback = function () {
13 createdElements.push(this.id);
14 };
15
16 document.register('x-b', {prototype: protoB});
17 shouldBe("createdElements", "['elemA0', 'elemB0']");
18 };
19
20 document.register('x-a', {prototype: protoA});
21 </script>
22 <x-b id=elemB0></x-b>
23 <x-a id=elemA0></x-a>
24 <x-b id=elemB1></x-b>
25 <script>
26 shouldBe("createdElements", "['elemA0', 'elemB0', 'elemB1']");
27 </script>
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698