Open Bug 1962159 Opened 25 days ago Updated 24 days ago

The “format” attribute is not part of the “Save to Pocket” and “Dismiss” telemetry probes

Categories

(Firefox :: New Tab Page, defect)

Desktop
All
defect

Tracking

()

Tracking Status
firefox137 --- unaffected
firefox138 --- unaffected
firefox139 --- affected

People

(Reporter: cfat, Assigned: maxx)

References

(Blocks 1 open bug)

Details

(Whiteboard: [hnt])

[Affected versions]:

  • Firefox Nightly 139.0a1 (Build ID: 20250422213740)

[Affected Platforms]:

  • Windows 11 x64
  • Ubuntu 24.04 x64
  • macOS 15.3

[Prerequisites]:

  • Have Firefox Nightly 138 installed.
  • Set the following prefs set to true:
    -> browser.newtabpage.activity-stream.discoverystream.sections.enabled
    -> browser.newtabpage.activity-stream.discoverystream.sections.cards.enabled
    -> browser.newtabpage.activity-stream.discoverystream.sections.cards.thumbsUpDown.enabled
    -> browser.search.region = US
  • Have Glean already configured and a custom tag set.

[Steps to reproduce]:

  1. Open the browser with the profile from the prerequisites.
  2. Open a new tab.
  3. Click the “...” context menu button from a Pocket card.
  4. Click the “Dismiss” option.
  5. Navigate to the Glean debug page and from the set custom tag verify the latest "newtab" telemetry registered.
  6. Observe if the “Dismiss” telemetry probe content has the “format” attribute.

[Expected result]:

  • The “format” attribute is displayed and has a value (e.g. “small-card”).

[Actual result]:

  • The “format” attribute is not displayed.

[Notes]:

  • The issue is also reproducible with the "Save to Pocket” telemetry probe.
  • The "format" parameter should be displayed in the "Dismiss" and "Save to Pocket” telemetry probes as per the Test Plan.
  • This issue is not reproducible with the sponsored cards.
Blocks: 1962154
Assignee: nobody → mcrawford
Whiteboard: [hnt]

We can omit from “Save to Pocket” from this requirement/testing. Thank you!

For “Dismiss” - I'd put that as an S4, but if we can fix it while we're on this feature, that would be great.

See Also: → 1962404
You need to log in before you can comment on or make changes to this bug.