DescriptionEscape search terms correctly in the path portion of a custom search engine.
This regressed with the fix for bug 111923. This attempts to correct the problem without breaking that bug, which requires being able to encode path components using arbitrary encodings.
This also eliminates a variety of functions as cleanup:
* BrowserAccessibilityWin::Escape(); this was not actually used.
* The 4-arg form of EscapeQueryParamValue(); only template_url.cc used this, and the necessary implementation can just move there.
* EscapeQueryParamValueUTF8(); the few remaining callers using that can just manually convert on the caller side.
BUG=127475
TEST=Create custom search engine with url "http://google.com/%s", try using your custom engine to search for "foo/bar", and make sure you wind up at "google.com/foo/bar" and not "google.com/foo%2Fbar"
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=139929
Patch Set 1 #Patch Set 2 : #
Messages
Total messages: 8 (0 generated)
|