urlbar.bounce is never recorded for searches from the New Tab search bar
Categories
(Firefox :: Address Bar, defect, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox157 | --- | fixed |
People
(Reporter: dao, Assigned: dao)
References
Details
(Whiteboard: [sng][mcab-hnt])
Attachments
(3 files)
urlbar.bounce lists newtab_searchbar among its sap values, but no bounce is ever recorded for a search from the New Tab search bar.
Tracking starts in UrlbarInputBase.pickResult behind an if (this.window.gBrowser) whose comment leaves the content-process case open: "TBD if and how this should work for a moz-urlbar living in a content process." The triggers are the other half: handleBounceEventTrigger is called from _on_TabClose and from the tabs progress listener, both listeners on the chrome window's gBrowser, which the bar cannot reach from the content process.
browser/components/urlbar/tests/browser-newtab/browser_bounceTelemetry.js (bug 2068470) asserts the current behavior: neither navigating back nor closing the tab records a bounce, while the address bar in the same page does.
Updated•23 days ago
|
| Assignee | ||
Comment 1•23 days ago
|
||
One module-level map replaces the per-collector stores, so a trigger resolves the tab's bounce whichever input started it.
Behavior-neutral except in one spot: the direct path collects its snapshot before awaiting a prior bounce's trigger, where the engagement record that follows had already closed the view.
| Assignee | ||
Comment 2•23 days ago
|
||
| Assignee | ||
Updated•22 days ago
|
Updated•22 days ago
|
Updated•22 days ago
|
Updated•22 days ago
|
Updated•22 days ago
|
Comment 5•21 days ago
|
||
Backed out for causing failures at browser_glean_telemetry_bounce_sap.js.
Backout link: https://hg.mozilla.org/integration/autoland/rev/43ee5cbe2cb8
| Assignee | ||
Comment 6•21 days ago
|
||
A bounce records once the tab navigates away, by which point the address bar's sap no longer resolves to the page the search was made on: the direct path recorded a bounce as urlbar where its engagement had recorded urlbar_newtab. Keeping bounces in the parent-side store resolves the message path's sap at engagement time, leaving the two paths to disagree until this commit.
A bounce whose window closes before the trigger records too, where the closed window used to leave it without a sap. The sap test's urlbar expectation now matches the engagement sap test's, the first search of that session being on a blank page.
| Assignee | ||
Updated•21 days ago
|
Updated•18 days ago
|
Comment 8•18 days ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/fe54c180d124
https://hg.mozilla.org/mozilla-central/rev/fbe03de35a26
https://hg.mozilla.org/mozilla-central/rev/cbf2d2c6efc5
Updated•11 days ago
|
Description
•