Hook up urlbar result menu with suggest telemetry or event telemetry
Categories
(Firefox :: Address Bar, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox112 | --- | fixed |
People
(Reporter: dao, Assigned: dao)
References
(Blocks 1 open bug)
Details
(Whiteboard: [snt-urlbar-result-menu])
Attachments
(1 file)
Updated•2 years ago
|
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 1•2 years ago
|
||
From https://phabricator.services.mozilla.com/D166578#inline-919251:
This bypasses telemetry that's normally recorded when the user picks a Suggest help button. In general it bypasses any handling that's currently done by going through
UrlbarInput.pickResult()
. I think you'll need to do something likethis.input.pickResult(result, event, menuitem)
, but engagement telemetry isn't currently prepared to handle command events and menu item elements.
Assignee | ||
Comment 2•2 years ago
|
||
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 3•2 years ago
|
||
(In reply to Dão Gottwald [::dao] from comment #1)
This bypasses telemetry that's normally recorded when the user picks a Suggest help button. In general it bypasses any handling that's currently done by going through
UrlbarInput.pickResult()
. I think you'll need to do something likethis.input.pickResult(result, event, menuitem)
, but engagement telemetry isn't currently prepared to handle command events and menu item elements.
pickResult
is already quite complex, so I'm not sure expanding it to handle elements that aren't even selected view elements is a good idea. UrlbarInput
currently doesn't deal with the result menu at all. My impression is that there's not much of an existing path I could directly use, so it would really just add complexity. I put up a straw-man patch that makes the view invoke the controller's telemetry stuff directly instead of going through pickResult
. Does this seem reasonable?
Comment 4•2 years ago
|
||
You're right. Your patch is reasonable and seems a lot better than going through pickResult()
after all, thanks.
Updated•2 years ago
|
Comment 7•2 years ago
•
|
||
Backed out for causing mochitests failures in browser/components/urlbar/tests/browser-tips/browser_searchTips_interaction.js.
- Backout link
- Push with failures 1 ---> Retriggers and backfills
- Failure Log bc14
- Failure Log bc15
- Failure line bc14: TEST-UNEXPECTED-FAIL | browser/components/urlbar/tests/browser-tips/browser_searchTips_interaction.js | object in event urlbar#engagement#click must match. - "click" matches "enter" - {"filename":"resource://testing-common/TelemetryTestUtils.sys.mjs","name":"assertEvents","sourceId":602,"lineNumber":272,"columnNumber":16,"sourceLine":"","asyncCause":null,"asyncCaller":null,"caller":{"filename":"chrome://mochitests/content/browser/browser/compon
- Failure line bc15: TEST-UNEXPECTED-FAIL | browser/components/extensions/test/browser/browser_ext_urlbar.js | Test timed out -
Comment 9•2 years ago
|
||
Backed out changeset fcc4aae881d7 (bug 1790020) for causing bc failures at browser_ext_urlbar.js
Backout: https://hg.mozilla.org/integration/autoland/rev/9973259e69e777523ef59055a346dd439efe6f62
Failure log: https://treeherder.mozilla.org/logviewer?job_id=408375038&repo=autoland&lineNumber=6523
Comment 10•2 years ago
|
||
Comment 11•2 years ago
|
||
bugherder |
Assignee | ||
Updated•2 years ago
|
Description
•