1156078 - Google search problem with Tropicana 100%

Status: RESOLVED FIXED

(Web Compatibility :: Site Reports, defect)

Description

[shiladittyapaul]

User Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0
Build ID: 20150416143048

Steps to reproduce:

Firefox browser > search box>google search> "Tropicana 100%" without inverted commas


Actual results:

Automatically reload add 25 with it and reload then add 25 ..... process continue  


Expected results:

result should be there . should not happen the reload operation

Comment 1

[shiladittyapaul]

I think this is a glitch of Firefox browser

Comment 2

[Gert Van Waelvelde]

Mozilla/5.0 (Windows NT 6.1; rv:40.0) Gecko/20100101 Firefox/40.0

This issue is not a Firefox issue, but a Google Search issue.
I can reproduce this not only Nightly (2015-04-19), but also on Google Chrome 42 and Internet Explorer 11.

Comment 3

[:Gijs (he/him)]

Karl, do you know if we have contacts at Google we can talk to about this?

Comment 4

[Karl Dubost💡 :karlcow]

Attachment: tropicana-google-search

The issue is that I don't understand the bug report and how to reproduce. 

> Firefox browser > search box>google search> "Tropicana 100%" without inverted commas

* What are "inverted commas"?

> Automatically reload add 25 with it

* What does that mean?

:/ Sorry I'm confused.

The screenshot doesn't show anything unusual.

Comment 5

[Karl Dubost💡 :karlcow]

Attachment: search-google-percent

Ah! understood, it is happening on Google.com

Tropicana 100%

get URL encoded as:
https://www.google.com/search?q=Tropicana+100%25

but then get re-encoded again and again when displayed in the input.

Comment 6

[Karl Dubost💡 :karlcow]

Contacted Alex and Ryan at Google

Comment 7

[Karl Dubost💡 :karlcow]

Google team answer:

> I'm happy to report that the search team dug into this, 
> found the issue, and have posted a fix. We should expect 
> to see the fix pushed live by next week at the latest. 
> Let me know if you continue to see the issue!

Comment 8

[Mike Taylor [:miketaylr]]

Moving resolution to FIXED, because Google fixed this for us and indeed, it is fixed.