Removed WebTextCheckingResult legacy API use.

content/public/common/webkit_param_traits.h

Index: content/public/common/webkit_param_traits.h
diff --git a/content/public/common/webkit_param_traits.h b/content/public/common/webkit_param_traits.h
index 786b8ec9383575b9c68244e8e3ca4c88b5187742..ae58fbbd8dbf2ad5ea3fb4fb223e7caddd488e32 100644
--- a/content/public/common/webkit_param_traits.h
+++ b/content/public/common/webkit_param_traits.h
@@ -232,6 +232,14 @@ struct ParamTraits<WebInputEventPointer> {
 };
 
 template <>
+struct CONTENT_EXPORT ParamTraits<WebKit::WebString> {

[jam, 2012/02/10 18:00:09]

I think it was by design that we didn't have this before, i.e. we tried to avoid
using webkit types in chrome code, and only just when talking to WebKit API.

I'm CCing Darin for his thoughts.

+  typedef WebKit::WebString param_type;
+  static void Write(Message* m, const param_type& p);

[darin (slow to review), 2012/02/13 17:40:43]

yes, please please please don't add this.  WebString is not thread-safe.  you
should not be using it in chromium code except at the interface with WebKit.  it
is really too easy via PostTask to send a WebString to another thread.  that
will cause double-free bugs.

+  static bool Read(const Message* m, void** iter, param_type* p);
+  static void Log(const param_type& p, std::string* l);
+};
+
+template <>
 struct SimilarTypeTraits<WebKit::WebTextDirection> {
   typedef int Type;
 };