Make the parser an implementation detail of the Document

sky/engine/core/html/imports/HTMLImportLoader.cpp

Index: sky/engine/core/html/imports/HTMLImportLoader.cpp
diff --git a/sky/engine/core/html/imports/HTMLImportLoader.cpp b/sky/engine/core/html/imports/HTMLImportLoader.cpp
index 84ae5695b3a262c93f4e95f017d28f816fbe7c49..0b24a254b533cfca17bd67bd60ce583b2420149f 100644
--- a/sky/engine/core/html/imports/HTMLImportLoader.cpp
+++ b/sky/engine/core/html/imports/HTMLImportLoader.cpp
@@ -103,8 +103,7 @@ HTMLImportLoader::State HTMLImportLoader::startWritingAndParsing(mojo::URLRespon
         .withRegistrationContext(m_controller->master()->registrationContext());
     m_document = HTMLDocument::create(init);
     m_module = Module::create(contextDocument.get(), nullptr, m_document.get(), url.string());
-    m_document->startParsing();
-    m_document->parser()->parse(response->body.Pass());
+    m_document->startParsing()->parse(response->body.Pass());

[eseidel, 2014/11/12 19:02:14]

Should this just take the mojo pipe in the startParsing() call?

[abarth-chromium, 2014/11/12 21:13:57]

Yes, that would be sensible, but in a later CL in this series, I'm adding
another argument.  We can make startParsing pass these arguments through to the
parser, but it seemed easier to just return the parser...

     return StateLoading;
 }