Closed
Bug 1042604
Opened 10 years ago
Closed 4 years ago
Measure how many searches, for each engine, result in a final URL that can be parsed
Categories
(Firefox :: Search, defect, P4)
Firefox
Search
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: Paolo, Unassigned)
References
Details
(Whiteboard: [recent][metrics][fxsearch])
Every time a new search is started from one of the available locations in the browser, we start loading a known URL from the search engine, providing the search terms. The engine may then redirect to a different URL, so that the final location displayed in the address bar is different. We would like to know, in a distinct way for each search engine, how many times the final URL displayed in the address bar can be parsed back to the original search terms using the function defined in bug 1040721, and how many times this is not possible. We may want to detect the third case where the URL is recognized as a search but the terms do not match the original, which might be normal because of corrections made by the engine, or indicate an encoding issue. Search engines that use POST requests or redirects to a different path are currently expected to always fall into the "not possible" case for now, but this should still be measured. This has the requirement of distinguishing each engine, and has a similarity with the current total search count detection. Given this, we should determine whether we should use Firefox Health Report or Telemetry with a defined histogram for each default engine.
Reporter | ||
Updated•10 years ago
|
QA Whiteboard: [qa+]
Flags: firefox-backlog+
Reporter | ||
Comment 1•10 years ago
|
||
Blake, I think this bug is related to the work you're doing in bug 1042604, though a bit more challenging.
Updated•9 years ago
|
Rank: 45
Priority: -- → P4
Whiteboard: [recent][metrics][fxsearch]
Comment 2•4 years ago
|
||
There's no reason specified in comment 0 as to why we wanted this - why we needed to measure it. It has been 6 years, and I don't see a fresh demand for it at the moment, so I'm going to close this out.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•