Script for exporting WPT

third_party/WebKit/LayoutTests/imported/wpt/html/semantics/scripting-1/the-template-element/template-element/node-document-changes.html

Index: third_party/WebKit/LayoutTests/imported/wpt/html/semantics/scripting-1/the-template-element/template-element/node-document-changes.html
diff --git a/third_party/WebKit/LayoutTests/imported/wpt/html/semantics/scripting-1/the-template-element/template-element/node-document-changes.html b/third_party/WebKit/LayoutTests/imported/wpt/html/semantics/scripting-1/the-template-element/template-element/node-document-changes.html
index 8027fbb919617ba9c118adfcd8a250544441fc80..0c60c10738d8eaba9687e6ab0fabeea91aee9a87 100644
--- a/third_party/WebKit/LayoutTests/imported/wpt/html/semantics/scripting-1/the-template-element/template-element/node-document-changes.html
+++ b/third_party/WebKit/LayoutTests/imported/wpt/html/semantics/scripting-1/the-template-element/template-element/node-document-changes.html
@@ -14,7 +14,6 @@
 <div id="log"></div>
 <script type="text/javascript">
 
-

[foolip, 2016/11/01 22:07:44]

Good changes to test this with, but do you intend to land them together with the
script? In order to experiment with the process, I would rather think that you'd
first land these scripts, then do a separate CL with whitespace changes and do a
dry run to get the bots green. Then, when in the office, land it and run the
export scripts as soon as possible after landing. Make sense?

[jeffcarp, 2016/11/01 22:24:42]

This whitespace change made it into WPT master. Next time the WPT are imported
into Chromium this diff should go away.

[foolip, 2016/11/02 13:15:32]

Oh:
https://github.com/w3c/web-platform-tests/commit/96f559b2ee6a6c7133d1de6d5715...

That has a Cr-Commit-Position that doesn't have the corresponding change, does
the script notice this and exit requiring human intervention? This was obviously
deliberate, but this seems like just the thing that might happen by mistake and
cause changes to be lost.

Do you want to keep this to test the "same changes made on both sides" case?

[jeffcarp, 2016/11/03 23:54:07]

Sure, I'll keep this in mind.

 test(function() {
     var doc1 = newHTMLDocument();
     var template = doc1.createElement('template');
@@ -35,7 +34,6 @@ test(function() {
 }, 'Changing of template element\'s node document. ' +
     'Test that ownerDocument of an empty template and its content changes');
 
-
 test(function() {
     var doc1 = newHTMLDocument();
     doc1.body.innerHTML = '<template id="tmpl"><div>Div content</div> And some more text</template>';
@@ -63,7 +61,6 @@ test(function() {
 }, 'Changing of template element\'s node document. ' +
     'Test that ownerDocument of a not empty template and its content changes');
 
-
 test(function() {
     var doc1 = newHTMLDocument();
     doc1.body.innerHTML = ''
@@ -109,7 +106,6 @@ test(function() {
 }, 'Changing of template element\'s node document. ' +
     'Test that ownerDocument of nested template and its content changes');
 
-
 testInIFrame('../resources/template-contents.html', function(context) {
     var doc1 = context.iframes[0].contentDocument;
 
@@ -131,7 +127,6 @@ testInIFrame('../resources/template-contents.html', function(context) {
 }, 'Changing of template element\'s node document. ' +
     'Test document loaded from a file');
 
-
 testInIFrame('../resources/template-contents.html', function(context) {
     var doc1 = context.iframes[0].contentDocument;
 
@@ -161,7 +156,6 @@ testInIFrame('../resources/template-contents.html', function(context) {
 }, 'Changing of template element\'s node document. ' +
     'Adobt template element into a document that has a browsing context');
 
-
 testInIFrame('../resources/template-contents.html', function(context) {
     var doc1 = context.iframes[0].contentDocument;
 
@@ -173,7 +167,6 @@ testInIFrame('../resources/template-contents.html', function(context) {
 
     doc2.body.appendChild(template);
 
-
     assert_not_equals(template.ownerDocument, doc1,
             'Template node owner document should be changed');
     assert_not_equals(template.content.ownerDocument, templateContentOwner,