Set active document url to <template> content URL.

third_party/WebKit/Source/core/html/HTMLTemplateElement.cpp

Index: third_party/WebKit/Source/core/html/HTMLTemplateElement.cpp
diff --git a/third_party/WebKit/Source/core/html/HTMLTemplateElement.cpp b/third_party/WebKit/Source/core/html/HTMLTemplateElement.cpp
index d91e600906652e4841cea896870ab8790a0f90fe..a710b41f5db6302fa9a406e5dae2e38bd8a4b7c9 100644
--- a/third_party/WebKit/Source/core/html/HTMLTemplateElement.cpp
+++ b/third_party/WebKit/Source/core/html/HTMLTemplateElement.cpp
@@ -46,10 +46,12 @@ DEFINE_NODE_FACTORY(HTMLTemplateElement)
 HTMLTemplateElement::~HTMLTemplateElement() {}
 
 DocumentFragment* HTMLTemplateElement::content() const {
-  if (!content_)
+  if (!content_) {
     content_ = TemplateContentDocumentFragment::Create(
         GetDocument().EnsureTemplateDocument(),
         const_cast<HTMLTemplateElement*>(this));
+    content_->GetDocument().SetURL(GetDocument().Url());

[fs, 2017/04/25 09:13:45]

Shouldn't this rather be handled when creating the template document?

[foolip, 2017/04/25 09:23:44]

The relevant bit of spec:
https://html.spec.whatwg.org/multipage/scripting.html#template-contents
https://html.spec.whatwg.org/multipage/scripting.html#appropriate-template-co...

AFAICT, there's nothing that sets that document's URL.

[fs, 2017/04/25 10:20:47]

Right, https://dom.spec.whatwg.org/#interface-document only calls for 'setting'
the origin. (Maybe that should be asserted by the test as well then.)

[foolip, 2017/04/25 14:23:28]

Do you mean "The Document() constructor, when invoked, must return a new
document whose origin is the origin of current global object’s associated
Document"? It's a bit odd, but I'm pretty sure that is for the script-exposed
constructor only, and that when HTML says "Let /new doc/ be a new Document",
it's using a magical internal constructor.

[fs, 2017/04/25 14:39:26]

That may very well be the case. But shouldn't the magic internal constructor be
well-defined? (Based on the discrepancies observed here, one might argue that it
isn't.)

[fs, 2017/04/25 14:51:08]

Found what I was looking for:

'Unless stated otherwise, a document’s encoding is the utf-8 encoding, content
type is "application/xml", URL is "about:blank", origin is an opaque origin,
type is "xml", and its mode is "no-quirks".'

So, our current behavior seems right.

+  }
 
   return content_.Get();
 }