Closed Bug 2040918 Opened 11 days ago Closed 11 days ago

Fire button doesn't appear in 151 release despite Bug 1902686

Categories

(Firefox :: Private Browsing, defect, P1)

defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: manuel, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: regression)

Not sure if regressed by sematic is correct here. But the change should have been introduced by Bug 1902686.

  • ./mach mozregression --launch 151.0 (release) doesn't show the fire button in pbm and pref is false
  • ./mach mozregression --launch 2026-05-19 --repo mozilla-beta (152.0b1) shows the fire button and pref is true
  • ./mach mozregression --launch 2026-05-19 (nightly 153) shows the fire button in pbm and pref is true

There were some reports on reddit about the fire button not appearing and it has also been confirmed by QA.

Severity: -- → S2
Priority: -- → P1

The fire button also shows with the latest 151 beta: ./mach mozregression --launch 2026-05-14 --repo mozilla-beta. This is confusing

:emz, since you are the author of the regressor, bug 1902686, could you take a look?

For more information, please visit BugBot documentation.

Flags: needinfo?(emz)

It looks like an ongoing Nimbus rollout is pinning the feature pref to false. We're currently checking whether we can end or update that experiment.

Flags: needinfo?(emz)
See Also: → 2040953

We have ended the rollout that pinned the pref to false and replaced it with a rollout that only sets the feltPrivacy feature (needed for the pbm UX refresh). The fire button now shows up in release.

Status: NEW → RESOLVED
Closed: 11 days ago
Resolution: --- → FIXED

Set release status flags based on info from the regressing bug 1902686

Cleaning up the metadata since it wasn't a code change

No longer regressed by: 1902686
Resolution: FIXED → WORKSFORME
See Also: → 1902686
You need to log in before you can comment on or make changes to this bug.