Closed
Bug 762046
Opened 13 years ago
Closed 12 years ago
Amazon search-plugin hard-coded for desktop site; they send us mobile
Categories
(Firefox for Android Graveyard :: General, defect)
Tracking
(firefox14 wontfix, firefox15 wontfix, firefox16 wontfix, firefox17 wontfix, firefox18 verified, firefox19 verified, firefox20 verified, firefox-esr17 wontfix, fennec+)
People
(Reporter: aaronmt, Assigned: mfinkle)
References
Details
Attachments
(1 file)
3.24 KB,
patch
|
bnicholson
:
review+
akeybl
:
approval-mozilla-aurora+
akeybl
:
approval-mozilla-beta+
|
Details | Diff | Splinter Review |
Currently our Amazon search-plugin is hard-coded to send queries to their desktop site. While visiting Amazon manually sends us their mobile site (ie., Amazon.com redirects to http://www.amazon.com/gp/aw/h.html)
Example search: http://www.amazon.com/gp/aw/s/ref=is_box_?k=Sony
http://mxr.mozilla.org/mozilla-central/source/browser/locales/en-US/searchplugins/amazondotcom.xml
Reporter | ||
Updated•13 years ago
|
Reporter | ||
Updated•13 years ago
|
tracking-fennec: --- → ?
Reporter | ||
Comment 1•12 years ago
|
||
Any chance of getting a fix in for this?
Comment 2•12 years ago
|
||
I guess this has partnership impact, Kev?
Comment 3•12 years ago
|
||
Will need to coordinate with Amazon. I'll bring this up with Joanne and see what we should be including as a plugin.
Comment 4•12 years ago
|
||
We own the code for the search plug-in and Aaron has provided an example mobile search URL. Can we make the update with this information? What help do we need from Amazon?
Assignee | ||
Comment 5•12 years ago
|
||
I think we need the official URL Amazon would like us to use. We are currently using the same URL as Desktop Firefox uses.
Comment 6•12 years ago
|
||
(In reply to Mark Finkle (:mfinkle) from comment #5)
> I think we need the official URL Amazon would like us to use. We are
> currently using the same URL as Desktop Firefox uses.
Is this for tracking/partnership? Can we update the search plug-in to the URL that Aaron suggests to produce a good user experience now and update the URL again once we have an official one from Amazon?
Comment 7•12 years ago
|
||
I have contacted Amazon and will update the bug as soon as I get a response.
Comment 8•12 years ago
|
||
I am still working on this, hope to have an answer by Wed. (7/18). Thanks, Joanne
Assignee | ||
Updated•12 years ago
|
tracking-fennec: ? → 16+
Comment 9•12 years ago
|
||
I emailed them again yesterday asking for a contact to assist - no response so far.
Comment 10•12 years ago
|
||
I have been pushing on this regularly. I have a commitment from my contact to provide an update and/or solution by end of day Wed. (8/1)
Assignee | ||
Comment 11•12 years ago
|
||
Any update?
Updated•12 years ago
|
Keywords: productwanted
Comment 12•12 years ago
|
||
No, I have sent another request - our meetings have been rescheduled and cancelled the past 2 weeks.
Reporter | ||
Updated•12 years ago
|
status-firefox17:
--- → affected
status-firefox18:
--- → affected
Comment 13•12 years ago
|
||
Do we have any data on how many people are using the built in Amazon search option? If there are a significant number of users for this search integration, can we revisit providing them a good experience now with the mobile search URL that Aaron provided in the description until we get the official URL from Amazon?
Comment 14•12 years ago
|
||
We're generally not adding hooks to 3rd parties without their consent, as we want to be sure that the hardware on the other side is built out to handle the load etc. Not saying that this is a big problem in this case, but it's also hard to rule out from the outside.
Assignee | ||
Updated•12 years ago
|
tracking-fennec: 16+ → +
Comment 15•12 years ago
|
||
Hi,
Finally got a response from Amazon, they would prefer that we use: http://m.amazon.com
Let me know if there is anything else...
Thanks,
Joanne
Reporter | ||
Updated•12 years ago
|
status-firefox19:
--- → affected
Comment 16•12 years ago
|
||
(In reply to Joanne Nagel from comment #15)
> Hi,
>
> Finally got a response from Amazon, they would prefer that we use:
> http://m.amazon.com
>
Does this include tablet devices?
Flags: needinfo?(jnagel)
Assignee | ||
Comment 18•12 years ago
|
||
Using the non-desktop, non-mobile URL seems to send us to desktop for tablets and mobile for phones. Let's use that URL.
tracking-fennec: ? → +
Reporter | ||
Updated•12 years ago
|
Assignee: nobody → mark.finkle
Reporter | ||
Comment 19•12 years ago
|
||
http://www.amazon.com
Phones - Amazon (mobile)
Tablet 7" - Amazon (deskop)
Tablet 10" - Amazon (desktop)
Comment 20•12 years ago
|
||
Hi,
Finally received confirmation that m.amazon.com should be used for tablets as well. Is this an issue? Can we close this bug now?
Thanks,
Joanne
Flags: needinfo?(jnagel)
Reporter | ||
Updated•12 years ago
|
status-firefox20:
--- → affected
Assignee | ||
Comment 21•12 years ago
|
||
This patch uses: http://m.amazon.com/gp/aw/s&k={searchterm}
This means we will get mobile search results on tablets
Attachment #685270 -
Flags: review?(bnicholson)
Assignee | ||
Comment 22•12 years ago
|
||
Comment on attachment 685270 [details] [diff] [review]
patch
>+ dump("**** search engine url: " + url)
Oops. I'll remove this.
Updated•12 years ago
|
Attachment #685270 -
Flags: review?(bnicholson) → review+
Assignee | ||
Comment 23•12 years ago
|
||
(In reply to Mark Finkle (:mfinkle) from comment #21)
> Created attachment 685270 [details] [diff] [review]
> patch
>
> This patch uses: http://m.amazon.com/gp/aw/s&k={searchterm}
http://m.amazon.com/gp/aw/s?k={searchterm}
Comment 24•12 years ago
|
||
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 20
Updated•12 years ago
|
Assignee | ||
Comment 26•12 years ago
|
||
Comment on attachment 685270 [details] [diff] [review]
patch
[Approval Request Comment]
Bug caused by (feature/regressing bug #):
User impact if declined: Desktop search UI on phones
Testing completed (on m-c, etc.): landed on m-c
Risk to taking this patch (and alternatives if risky): fairly small. limited to amazon search only
String or UUID changes made by this patch: none
Attachment #685270 -
Flags: approval-mozilla-beta?
Attachment #685270 -
Flags: approval-mozilla-aurora?
Comment 27•12 years ago
|
||
Seems like a low risk change - adding qawanted/verifyme to verify that we don't have any regressions around localized build behavior.
Updated•12 years ago
|
Attachment #685270 -
Flags: approval-mozilla-beta?
Attachment #685270 -
Flags: approval-mozilla-beta+
Attachment #685270 -
Flags: approval-mozilla-aurora?
Attachment #685270 -
Flags: approval-mozilla-aurora+
Comment 28•12 years ago
|
||
Reporter | ||
Updated•12 years ago
|
Keywords: productwanted,
qawanted,
verifyme
Comment 29•12 years ago
|
||
We don't release ESR mobile so wontfixing for esr17.
Updated•4 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•