[Android WebView] Implement WebSettings.{get|set}UseWideViewport

content/renderer/render_view_impl.cc

Index: content/renderer/render_view_impl.cc
diff --git a/content/renderer/render_view_impl.cc b/content/renderer/render_view_impl.cc
index 37d1011dc930132ba83deb303b2f85c65398c999..0bed08e39c1411ac57fbccec481a5b4bf84bc8ad 100644
--- a/content/renderer/render_view_impl.cc
+++ b/content/renderer/render_view_impl.cc
@@ -3217,6 +3217,7 @@ void RenderViewImpl::ProcessViewLayoutFlags(const CommandLine& command_line) {
   webview()->settings()->setFixedElementsLayoutRelativeToFrame(true);
 
   if (enable_viewport) {
+    webkit_preferences_.viewport_enabled = true;

[darin (slow to review), 2013/01/08 17:10:42]

It seems a little odd to be setting a WebPreferences member here in the
RenderViewImpl.  Normally, we initialize WebPreferences in the browser-side, and
then send those all down together when initializing a RenderViewImpl.  Maybe
this change suggests that we shouldn't be checking kEnableViewport in the
renderer, but instead checking that in the browser?

[mnaganov (inactive), 2013/01/08 18:14:44]

Yes, it does look odd to me as well. But as you can see, 'setViewportEnabled'
works together with other settings and even flags that are set directly on a
WebView (enableFixedLayoutMode, setFixedLayoutSize), so we will need to put more
things into WebPreferences and perhaps, move fixed layout parameters into
WebSettings. I can do that first, prior to this patch. 

     webview()->settings()->setViewportEnabled(true);
   } else if (enable_fixed_layout) {
     std::string str =