From e9e1cdd556b40a04637b7de3d839b2a596df47e3 Mon Sep 17 00:00:00 2001
From: Scott Main <smain@google.com>
Date: Thu, 1 Oct 2009 14:59:24 -0700
Subject: decode the search string before putting it into the search control.
 this fixes a safari-only bug in which encoded chars were inserted into the
 search string.

http://b/issue?id=2031559

Change-Id: Ie60902bafcbb327d488b921f8d3925aaf9ff0566
---
 docs/html/search.jd | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'docs/html/search.jd')

diff --git a/docs/html/search.jd b/docs/html/search.jd
index 838af03..8032b22 100644
--- a/docs/html/search.jd
+++ b/docs/html/search.jd
@@ -94,9 +94,9 @@ page.title=Search Results
 
       // when an event on the browser history occurs (back, forward, load) perform a search
       $(window).history(function(e, hash) {
-        var query = getQuery(hash);
+        var query = decodeURI(getQuery(hash));
         searchControl.execute(query);
-        $("#searchTitle").html("search results for <em>" + decodeURI(query) + "</em>");
+        $("#searchTitle").html("search results for <em>" + query + "</em>");
       });
 
       // forcefully regain key-up event control (previously jacked by search api)
-- 
cgit v1.1