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.
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.