Closed Bug 1806425 Opened 2 years ago Closed 2 years ago

Make value of "source" in Feature Callout and "page" in its telementry more consistent

Categories

(Firefox :: Messaging System, enhancement, P3)

enhancement

Tracking

()

VERIFIED FIXED
111 Branch
Tracking Status
firefox111 --- verified

People

(Reporter: mviar, Assigned: mviar)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

An explicit call to the showFeatureCallout method on a Callout instance must be added on-train before messages can be delivered on that page. Currently we support Feature Callouts in Firefox View and the PDF reader. In the Feature Callout telemetry, the value of page is reported as about:firefoxview for the former and chrome://browser/content/browser.xhtml for the latter (this is the browser chrome's url). While neither case currently exposes the URL of non-Firefox pages the user visits, we want to ensure that remains the case moving forward. This is especially true if we expand the user of the Feature Callout in the browser chrome. We also want the page values to be meaningful (not currently the case with the one for PDF.js).

The value of page currently comes from the Feature Callout instance's source (see here and here). For page event actions, the value of page in telemetry is currently set to the documents location href (see here). These implementations should be unified to ensure we're reporting a consistent value for a given Callout instance.

We can use a token like "CHROME" for the source/page value when showing a Feature Callout in the browser chrome.

Priority: -- → P3
Summary: Use tokens for "page" value in Feature Callout telemetry → Make value of "source" in Feature Callout and "page" in its telementry more consistent
Assignee: nobody → mviar
Attachment #9310579 - Attachment description: WIP: Bug 1806425 - Make value of source in Feature Callout and page in its telementry more consistent → Bug 1806425 - Make value of source in Feature Callout and page in its telementry more consistent

There's a r+ patch which didn't land and no activity in this bug for 2 weeks.
:mviar, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit auto_nag documentation.

Flags: needinfo?(mviar)
Flags: needinfo?(jprickett)

I've been OOO for the last two weeks, but just requested landing.

Flags: needinfo?(mviar)
Flags: needinfo?(jprickett)
Pushed by mviar@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/00d212a6a60f Make value of source in Feature Callout and page in its telementry more consistent r=jprickett,aminomancer
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED
Target Milestone: --- → 111 Branch

I have verified this enhancement using the steps provided here and I can confirm the following:

  • the "page" value for spotlights is: "spotlight"
  • the "page" value for "Feature Callout for PDF.js" messages is: "chrome"
  • the "page" value for "Feature Callout for about:firefoxview" messages is: "about:firefoxview"
  • the "page" value for the "about:welcome" page is: "about:welcome".

Verified using the latest Firefox Nightly (111.0a1 Build ID - 20230131093335) installed on Windows 10 x64, macOS 12.6.1, and Ubuntu 22.04 x64.

Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: