Test urlbar engagement and abandonment telemetry for the New Tab search bar
Categories
(Firefox :: Address Bar, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox157 | --- | fixed |
People
(Reporter: dao, Assigned: dao)
References
Details
(Whiteboard: [sng][mcab-hnt])
Attachments
(4 files)
Nothing asserts the urlbar.engagement or urlbar.abandonment metrics for the New Tab search bar. newtab_searchbar is a documented sap value in browser/components/urlbar/metrics.yaml and UrlbarParentController carries the branch that produces it, but the sap matrix in browser/components/urlbar/tests/browser-engagementTelemetry/ covers urlbar, urlbar_newtab, searchbar, handoff and urlbar_addonpage only.
browser/components/urlbar/tests/browser-newtab/browser_searchTelemetry.js does not overlap. It asserts newtabSearch.issued, the SAP counters and the SERP ad metrics, and touches no urlbar.* metric.
Worth asserting:
sapon engagement and abandonment.abandonment_type. The bar lives in the page, so a tab switch or a navigation destroys it where the address bar survives, andblurresolves differently fromtab_switch.groups,resultsandn_results.newtab_searchbarhas its own provider set - no Places, InputHistory, RemoteTabs, TopSites or TabToSearch - so its result composition matches neitherurlbarnorsearchbar, and its result-groups branch inUrlbarPrefsis marked in-tree as a placeholder.urlbar.disable. The bar carriesUrlbarProviderQuickSuggest, so unlikesearchbarandhandoffit can record one.urlbar.bounce, for a bar hosted in the page the user navigates away from and back to.
The tests belong in browser/components/urlbar/tests/browser-newtab/, which already has NewtabSearchbarTestUtils wired and loads the same head-common.js; only the assertGleanTelemetry helpers need lifting. A mirror of doHandoffTest() in browser-engagementTelemetry/ is not the shape: that helper turns the New Tab search bar off and drives gURLBar, so every drive verb there (openPopup, doBlur, doEnter, doClick, doTest) would need a browser-taking parallel.
Updated•25 days ago
|
| Assignee | ||
Comment 1•25 days ago
|
||
Updated•25 days ago
|
| Assignee | ||
Comment 2•25 days ago
|
||
Reading the details of a search result threw "Something tried to use the search service before it finished initializing", since the content-side utils resolved the url themselves.
| Assignee | ||
Comment 3•25 days ago
|
||
The bar records no urlbar.bounce (bug 2068488), so browser_bounceTelemetry.js asserts that absence with the address bar in the same page as its control.
Updated•25 days ago
|
Updated•25 days ago
|
| Assignee | ||
Comment 4•25 days ago
|
||
tab_switch reads as "the user switched tabs", but the address bar records it only for a session it keeps focus through; a switch that takes focus out of the input records blur, and so does the New Tab search bar's, which goes into the background with its page.
Updated•24 days ago
|
Comment 7•24 days ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/8d872380da6a
https://hg.mozilla.org/mozilla-central/rev/d10d1bdec2e5
https://hg.mozilla.org/mozilla-central/rev/a5a9d8186da1
https://hg.mozilla.org/mozilla-central/rev/4e9c6db9c34a
Updated•24 days ago
|
Description
•