Closed Bug 786873 Opened 12 years ago Closed 12 years ago

Format change for Google search suggest JSON

Categories

(Firefox :: Search, defect)

defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: mgraboski, Assigned: MattN)

Details

The Google search team is planning on slightly changing the format of the JSON data returned by the Google search suggestions URL.  Specifically, they're changing the data type of the third field in the JSON from a standard field to an array of integers.  

If Firefox doesn't use this field for parsing search suggestions, or if Firefox doesn't perform strict validation of the JSON returned by search suggest (e.g., validating that every field in the JSON exists and is a certain data type), then there probably won't be an impact.

Would someone in the Firefox developer community be able to test the impact of the search suggest changes?  To do this, simply append "&gf_ns=3" to your existing search suggest URL.    If you could post any updates to this bug in the next few days, that will be very helpful to let the search team know if this change will adversely affect Firefox.
Assignee: nobody → mnoorenberghe+bmo
Hardware: x86 → All
(In reply to Mike Graboski from comment #0)
> The Google search team is planning on slightly changing the format of the
> JSON data returned by the Google search suggestions URL.  Specifically,
> they're changing the data type of the third field in the JSON from a
> standard field to an array of integers.  

Which queries should be returning the third field?  None of these URLs I tested returned a third field:

* https://www.google.com/complete/search?client=firefox&q=mozilla
* https://www.google.com/complete/search?client=firefox&q=mozilla&gf_ns=3
* https://www.google.com/complete/search?client=firefox&q=google&gf_ns=3
* https://www.google.com/complete/search?client=firefox&q=firefox&gf_ns=3

Are there some sample URLs you could provide that show the changes?
As it turns out, this change will not affect Firefox search suggestions at all.  Sorry for the confusion!
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.