Closed
Bug 305925
Opened 19 years ago
Closed 19 years ago
Firefox does not return the same results for any search - IE & NS show current search results & current adwords
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: claudia, Unassigned)
References
()
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 FF Browser & google.com search for any keywords does not sure current google listings & adwords - IE & NS google.com search does show current listings and adwords. I've noticed this for the last couple weeks, going crazy as to why my adwords where not showing up. They do when using IE or NS browseres & google.com Reproducible: Always Steps to Reproduce: 1.OPen FF - use google.com - search key word "nipple jewelry" Odd listings & old adwords 2.Open IE - use google.com - search keyword "nipple jewelry" Current listings & adwords 3.Open NS - use google.com - search keyword "nipple jewelry" Current listings & adwords. Actual Results: see above, sample keyword search. FireFox browser seems to return old or odd results. Definately not current listings nor adwords. Expected Results: shown the same "current" results as found when using IE and/or NS Bug may be minor to you, but to companies paying for adwords and/or top ten listings are losing sales from customers using FoxFire browser, this is a MAJOR problem.
WFM in 1.0.6. Seems pretty unlikely - FF can only send the search to ggole like any other browser.
Comment 2•19 years ago
|
||
I really have no idea how you know that the ads listed are the "current" ones, considering that you don't know how Google chooses the ads to display. Just because Firefox and IE show different ads, it doesn't mean that this is a bug in Firefox.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → INVALID
Updated•19 years ago
|
Summary: FireFox does not return the same results for any search - IE & NS show current search results & curent adwords → Firefox does not return the same results for any search - IE & NS show current search results & curent adwords
Updated•19 years ago
|
Summary: Firefox does not return the same results for any search - IE & NS show current search results & curent adwords → Firefox does not return the same results for any search - IE & NS show current search results & current adwords
I have tried various random words, but have only had luck with any wording containing 'nipples' ...wierd. I've tried 'car tires' - 'home loans' - 'plastic bags' - all the same. BUT googling 'plastic nipples' and FF is different than IE & NS.... really wierd.
Status: RESOLVED → UNCONFIRMED
Resolution: INVALID → ---
'breast lift' is also different from FF in NS & IE Is it possible there is some kind of 'rating control'???? although I don't see how plastic nipple would fall under a rating
Comment 5•19 years ago
|
||
I tried FF 1.0.6, Deerpark, Deerpark with MSIE ua string, and MSIE and get pretty much the same results for each of the "nipple jewelry" and "plastic nipples". I have never searched for these terms before, but considering this is your business you probably have. Can you clear your cache (under tools->options->privacy) and see if you get newer results?
Comment 6•19 years ago
|
||
Do you have the Google Toolbar installed in IE? I tried a search for Toshiba laptops and only two results were the same. It sends this to the server: http://www.google.com/search?sourceid=navclient&gfns=1&ie=UTF-8&q=toshiba+laptop When I pasted this into Firefox locationbar the results were the same. The results were also the same when I uninstalled IE's Google Toolbar.
Comment 7•19 years ago
|
||
Comment 8•19 years ago
|
||
Comment 9•19 years ago
|
||
This is quite obviously not a problem within Firefox. Google mentions on their site that results will vary from search to search. Resolving INVALID.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago → 19 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•