Closed
Bug 1979089
Opened 1 year ago
Closed 1 year ago
The "IP_PROTECTION_INTRODUCTION_CALLOUT_FIRST" callout is not naturally triggered
Categories
(Firefox :: IP Protection, defect)
Tracking
()
VERIFIED
FIXED
143 Branch
| Tracking | Status | |
|---|---|---|
| firefox141 | --- | unaffected |
| firefox142 | --- | unaffected |
| firefox143 | --- | verified |
People
(Reporter: mcoman, Assigned: rking)
References
Details
(Whiteboard: [fx-vpn])
Attachments
(1 file)
[Affected versions]:
- Firefox Nightly 142.0a1 - Build ID: 20250724093417
[Affected Platforms]:
- Windows 10 x64
[Prerequisites]:
- Have a new Firefox profile created.
[Steps to reproduce]:
- Open the browser using the profile from the prerequisites.
- Navigate to the "about:config" page and set the
browser.ipProtection.enabledpref totrue. - Restart the browser and observe the behavior.
[Expected result]:
- The "IP_PROTECTION_INTRODUCTION_CALLOUT_FIRST" callout is triggered in the top-right part of the browser.
[Actual result]:
- The "IP_PROTECTION_INTRODUCTION_CALLOUT_FIRST" callout is not triggered at all.
[Notes]:
- After further investigation, it seems that this issue might be caused by the fact that the
(messageImpressions.IP_PROTECTION_INTRODUCTION_CALLOUT_SECOND.lengthimpression is not set.
Pushed by rking@mozilla.com:
https://github.com/mozilla-firefox/firefox/commit/873bffdb8951
https://hg.mozilla.org/integration/autoland/rev/0437590aba88
Ensure that first IP protection callout is triggered - r=ip-protection-reviewers,omc-reviewers,mviar,Gijs
Comment 3•1 year ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 143 Branch
| Reporter | ||
Comment 4•1 year ago
|
||
I have verified that this issue is no longer reproducible using the latest Firefox Nightly 143.0a1 (Build ID: 20250813091044) installed on Windows 10 x64. I can confirm that the "IP_PROTECTION_INTRODUCTION_CALLOUT_FIRST" callout is successfully triggered.
Status: RESOLVED → VERIFIED
Updated•1 year ago
|
Whiteboard: [fx-vpn]
Updated•1 year ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•