Closed Bug 2068488 Opened 23 days ago Closed 18 days ago

urlbar.bounce is never recorded for searches from the New Tab search bar

Categories

(Firefox :: Address Bar, defect, P1)

defect

Tracking

()

RESOLVED FIXED
157 Branch
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.

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.

See Also: → 2068796
Assignee: nobody → dao+bmo
Status: NEW → ASSIGNED
Attachment #9635682 - Attachment description: WIP: Bug 2068488 - Keep every urlbar bounce in one parent-side store keyed by the tab. r?daleharvey! → Bug 2068488 - Keep every urlbar bounce in one parent-side store keyed by the tab. r?daleharvey!
Attachment #9635683 - Attachment description: WIP: Bug 2068488 - Record urlbar.bounce for the New Tab search bar. r?daleharvey! → Bug 2068488 - Record urlbar.bounce for the New Tab search bar. r?daleharvey!
Attachment #9635683 - Attachment description: Bug 2068488 - Record urlbar.bounce for the New Tab search bar. r?daleharvey! → Bug 2068488 - Record urlbar.bounce for the New Tab search bar. r?mbeier!
Attachment #9635682 - Attachment description: Bug 2068488 - Keep every urlbar bounce in one parent-side store keyed by the tab. r?daleharvey! → Bug 2068488 - Keep every urlbar bounce in one parent-side store keyed by the tab. r?mbeier!
See Also: → 2069403
See Also: → 2069402
Pushed by abutkovits@mozilla.com: https://github.com/mozilla-firefox/firefox/commit/29349bf94fd2 https://hg.mozilla.org/integration/autoland/rev/43ee5cbe2cb8 Revert "Bug 2068488 - Record urlbar.bounce for the New Tab search bar. r=mbeier" for causing failures at browser_glean_telemetry_bounce_sap.js.

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.

Flags: needinfo?(dao+bmo)
Severity: -- → S4
Priority: -- → P1
Status: ASSIGNED → RESOLVED
Closed: 18 days ago
Resolution: --- → FIXED
Target Milestone: --- → 157 Branch
Duplicate of this bug: 2068796
QA Whiteboard: [qa-triage-done-c158/b157]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: