Closed Bug 1816923 Opened 3 years ago Closed 3 years ago

[Experiment] The Treatment B branch of the “PDFjs Feature Callout” experiment displays the wrong impression pings

Categories

(Firefox :: Messaging System, defect)

Desktop
All
defect

Tracking

()

VERIFIED FIXED
Tracking Status
firefox110 --- verified

People

(Reporter: avarro, Unassigned)

References

(Blocks 1 open bug)

Details

[Affected versions]:

  • Firefox Release 110.0 - Build ID: 20230214051806

[Affected Platforms]:

  • Windows 10 x64.
  • macOS 13.1.
  • Linux Mint 20.2 x64.

[Prerequisites]:

  • Have the “nimbus.debug” and “browser.ping-centre.log” prefs set to true on the “about:config” page.
  • Have the browser console opened (Ctrl/Cmd + Shift +J).

[Steps to reproduce]:
1.Navigate to the “about:studies?optin_slug=pdfjs-feature-callout&optin_branch=treatment-b&optin_collection=nimbus-preview” URL to force enroll in the Treatment B branch of the “PDFjs Feature Callout” experiment.
2. Navigate to a page that ends in “.pdf” (e.g.:https://www.clickdimensions.com/links/TestPDFfile.pdf ).
3. Focus the Browser console.
4. Observe the displayed telemetry pings for the first slide.

[Expected result]:

  • The "PDFJS_FEATURE_TOUR_0_FEATURE_CALLOUT_1_B_C" is displayed in the Browser Console.

[Actual result]:

  • The "PDFJS_FEATURE_TOUR_0_FEATURE_CALLOUT_1_A_C" is displayed in the Browser Console.

[Notes]:

  • This issue is also reproducible for the second slide.
  • This issue is also reproducible for the “Click” telemetry pings.
  • Attaching a screen recording of the issue here.

This has the same cause as the issue reported in bug 1816905. The experiment was misconfigured to show the Treatment A messages for both branches A and B.

The experiment recipe has been updated to correctly use FEATURE_CALLOUT_1_B in treatment branch B.

I'm marking this as RESOLVED - FIXED based on Jason's comment.

Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED

I have verified this issue using the latest Firefox Release 110.0 (Build ID: 20230214051806) on Windows 10x64, macOS 12.6 and Linux Mint 20.2x64 and I can confirm that the Treatment B branch of the "PDFjs Feature Callout" experiment displays the correct telemetry pings in the Browser Console.

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