1817156 - In engagement telemetry when engagement_type is a _go one, selected_result is unknown

Status: VERIFIED FIXED

(Firefox :: Address Bar, defect, P2)

Description

[Marco Bonardo [:mak]]

paste_go and drop_go are two engagement_type values that won't have a selected_result, because we don't show the view for them.
We should document this fact in the metric documentation.
Whether we want to use an empty string, unknown or a special input_field value, is something I asked Rebecca about, let's wait for an answer.

Comment 1

[Daisuke Akatsuka (:daisuke)]

Attachment: Bug 1817156: Use input_field as selected_result value if the result view has not been shown upon engagement

Depends on D170143

Comment 2

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/f646c0e02734
Use input_field as selected_result value if the result view has not been shown upon engagement r=mak

Comment 3

[Serban Stanca [:SerbanS]]

https://hg.mozilla.org/mozilla-central/rev/f646c0e02734

Comment 4

[Cristian Baica [:cbaica], Release Desktop QA]

Issue is verified fixed in the latest Fx 112.0a1 on Windows 10 and Ubuntu 20. "paste_go" and "drop_go" enagements have the selected_result listed as "input_field".