Expose way to enable/disable translate.

ios/web_view/public/cwv_web_view_configuration.h

Index: ios/web_view/public/cwv_web_view_configuration.h
diff --git a/ios/web_view/public/cwv_web_view_configuration.h b/ios/web_view/public/cwv_web_view_configuration.h
index e1de0986ae24ad7206ab2b9b7064b48bcaa473fb..76145c87f1f4f20af728e37a6a3727bef13ac8e8 100644
--- a/ios/web_view/public/cwv_web_view_configuration.h
+++ b/ios/web_view/public/cwv_web_view_configuration.h
@@ -9,6 +9,7 @@
 
 #import "cwv_export.h"
 
+@class CWVTranslationConfiguration;
 @class CWVUserContentController;
 @class CWVWebsiteDataStore;
 
@@ -24,6 +25,10 @@ CWV_EXPORT
 
 - (instancetype)init NS_UNAVAILABLE;
 
+// Allows configuration of translation settings.
+@property(nonatomic, readonly)
+    CWVTranslationConfiguration* translationConfiguration;

[Eugene But (OOO till 7-30), 2017/07/14 00:22:43]

In Objective-C, configuration objects are used to configure other objects (e.g.
initialize them). So I don't think we should use configuration name here. How
about CWVTranslationPreferences or just CWVPreferences (similar to
WKPreferences)?

[Hiroshi Ichikawa, 2017/07/14 01:18:39]

I would slightly prefer CWVTranslationPreferences because I prefer to isolate
translation specific features to its own classes. But either is fine for me.

[jzw1, 2017/07/14 02:09:50]

Going to call this new thing CWVPreferences.

+
 // The user content controller to associate with web views created using this
 // configuration.
 @property(nonatomic, readonly) CWVUserContentController* userContentController;