Closed Bug 1790020 Opened 2 years ago Closed 2 years ago

Hook up urlbar result menu with suggest telemetry or event telemetry

Categories

(Firefox :: Address Bar, task)

task
Points:
3

Tracking

()

RESOLVED FIXED
112 Branch
Tracking Status
firefox112 --- fixed

People

(Reporter: dao, Assigned: dao)

References

(Blocks 3 open bugs)

Details

(Whiteboard: [snt-urlbar-result-menu])

Attachments

(1 file)

No description provided.

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 like this.input.pickResult(result, event, menuitem), but engagement telemetry isn't currently prepared to handle command events and menu item elements.

Assignee: nobody → dao+bmo
Status: NEW → ASSIGNED

(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 like this.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?

Flags: needinfo?(adw)

You're right. Your patch is reasonable and seems a lot better than going through pickResult() after all, thanks.

Flags: needinfo?(adw)
Blocks: 1804558
Attachment #9315626 - Attachment description: WIP: Bug 1790020 - Hook up urlbar result menu with telementry. → Bug 1790020 - Hook up urlbar result menu with telementry. r=mak
Blocks: 1820825
Pushed by dgottwald@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/e7822e311e0c Hook up urlbar result menu with telementry. r=mak
Backout by sstanca@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/0734dc2a0dac Backed out changeset e7822e311e0c for causing mochitests failures in browser/components/urlbar/tests/browser-tips/browser_searchTips_interaction.js. CLOSED TREE

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 -
Flags: needinfo?(dao+bmo)
Pushed by dgottwald@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/fcc4aae881d7 Hook up urlbar result menu with telementry. r=mak
Pushed by dgottwald@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/4e06f5ee4dd4 Hook up urlbar result menu with telementry. r=mak
Blocks: 1821375
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
Blocks: 1819070
Blocks: 1819071
Flags: needinfo?(dao+bmo)
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: