DomDistiller: fix 0 document width

components/dom_distiller/webui/dom_distiller_ui.cc

Index: components/dom_distiller/webui/dom_distiller_ui.cc
diff --git a/components/dom_distiller/webui/dom_distiller_ui.cc b/components/dom_distiller/webui/dom_distiller_ui.cc
index 436e6574c57581daee3edffa78d4462286f41057..9d82b0139f74f888ab619f06aec17df6214068fc 100644
--- a/components/dom_distiller/webui/dom_distiller_ui.cc
+++ b/components/dom_distiller/webui/dom_distiller_ui.cc
@@ -52,7 +52,8 @@ DomDistillerUi::DomDistillerUi(content::WebUI* web_ui,
   source->SetJsonPath("strings.js");
 
   // Add message handler.
-  web_ui->AddMessageHandler(new DomDistillerHandler(service, scheme));
+  web_ui->AddMessageHandler(new DomDistillerHandler(service, scheme,
+      web_ui->GetWebContents()->GetContainerBounds().size()));

[nyquist, 2014/07/15 17:13:03]

What would happen if the user resizes the browser before opening an article?
Could this be done on-the-fly in the handler instead of stored as a member?

[Yaron, 2014/07/16 17:46:28]

Agreed. I thought these handlers were actually long-lived (not just for a single
chrome:// page) so instead use web_ui()->GetWebContents() in |HandleAddArticle|

[nyquist, 2014/07/16 19:20:49]

I think they're created through |WebContentsImpl::CreateWebUI ->
ChromeWebUIControllerFactory::CreateWebUIControllerForURL -> DomDistillerUi
factory function| which is used by RenderFrameHostManager::SetPendingWebUI which
is called during navigation of a RenderFrame, so I think it's linked to the
RenderFrame navigation entry lifetime, so not long-lived-forever.

Anyway, the previous comments still apply.

[kuan, 2014/07/17 09:57:26]

Done.

 }
 
 DomDistillerUi::~DomDistillerUi() {}