Fix search term encoding
Fix for incorrect handling of encodings used for search terms. TemplateURL::EncodeSearchTerms function was always using first passed codepage instead of trying to use passed codepages in the order provided, as stated in online docs for DefaultSearchProviderEncodings policy. Bug: 582756 Change-Id: I659f82f0e777c950a888e2ceff8726c4fdcf0378 Reviewed-on: https://chromium-review.googlesource.com/922621 Commit-Queue: Alexander Yashkin <a-v-y@yandex-team.ru> Reviewed-by:Peter Kasting <pkasting@chromium.org> Cr-Commit-Position: refs/heads/master@{#537547}
Showing
Please register or sign in to comment