You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's a problem with the encoding of special characters when searching through the box. I think it could be an issue with the encoding taking place at socket.io that can be seen on the screenshot below. Look at byteString, the original input (ó) became another character.
Then at the Google search URL the (ó) becomes: (%F3) which in turn becomes a question mark sign (?) on the google results page.
The text was updated successfully, but these errors were encountered:
the reason for this wrong conversion is the string "ie=UTF-8" that gets added to the escaped search url in box.js - without this or alternatively without escaping the search term it works as expected
There's a problem with the encoding of special characters when searching through the box. I think it could be an issue with the encoding taking place at socket.io that can be seen on the screenshot below. Look at
byteString
, the original input (ó) became another character.Then at the Google search URL the (ó) becomes: (%F3) which in turn becomes a question mark sign (?) on the google results page.
The text was updated successfully, but these errors were encountered: