Stop using the escape function for descriptions on the search result page

Apparently escape is deprecated, and it's also introducing some issues. We may encounter other descriptions with problems as a result of this, but they should be fixed in a different way.

1 files changed, 4 insertions, 4 deletions

diff --git a/gn2/wqflask/templates/search_result_page.html b/gn2/wqflask/templates/search_result_page.html
index aad7fd99..334dbc77 100644
--- a/gn2/wqflask/templates/search_result_page.html
+++ b/gn2/wqflask/templates/search_result_page.html
@@ -238,9 +238,9 @@
                   description = data.description.slice(0, 200) + '...'
                 }
                 try {
-                  return decodeURIComponent(escape(description))
+                  return decodeURIComponent(description)
                 } catch(err){
-                  return escape(description)
+                  return description
                 }
               }
             },
@@ -306,9 +306,9 @@
                   description = data.description.slice(0, 200) + '...'
                 }
                 try {
-                  return decodeURIComponent(escape(description))
+                  return decodeURIComponent(description)
                 } catch(err){
-                  return escape(description)
+                  return description
                 }
               }
             },