Support fixed prefixes and suffixes when extracting terms from search template URLs.

components/search_engines/template_url.h

Index: components/search_engines/template_url.h
diff --git a/components/search_engines/template_url.h b/components/search_engines/template_url.h
index c62bd20bea689c4c5cf5f7561428e73efa1ef41d..10bc6d44885ea415fcfec2e64e8b24d6a15b29bd 100644
--- a/components/search_engines/template_url.h
+++ b/components/search_engines/template_url.h
@@ -467,6 +467,8 @@ class TemplateURLRef {
   mutable std::string search_term_key_;
   mutable size_t search_term_position_in_path_;
   mutable url::Parsed::ComponentType search_term_key_location_;
+  mutable std::string search_term_value_prefix_;
+  mutable std::string search_term_value_suffix_;

[Peter Kasting, 2016/04/21 19:48:57]

I wonder if it would be any simpler/clearer to use a url::Component for this
instead, e.g.

  mutable url::Parsed::ComponentType search_term_key_component_;
  mutable url::Component search_term_value_location_;

[jbroman, 2016/04/21 21:01:42]

I don't understand; IIUC url::Component is a (begin, length) pair.

Suppose the query param is "prefix{searchTerms}suffix"; the beginning position
is fixed, but the length will vary (it will be the length of the actual search
terms, which varies).

[Peter Kasting, 2016/04/21 22:29:46]

Yeah, sorry, I was misconceiving how these were being used.

 
   mutable PostParams post_params_;