Learn more link for disabling telemetry opens two tabs
Categories
(Firefox :: Settings UI, defect, P3)
Tracking
()
People
(Reporter: mathew.hodson, Assigned: mathew.hodson)
References
(Regression)
Details
(Keywords: regression)
Attachments
(2 files)
Steps to reproduce:
- Go to about:preferences#privacy
- Enable "Allow Nightly to send technical and interaction data to Mozilla" if it isn't already
- Click the checkbox to then disable it
- Click the Learn more link in the info box that appears
Actual results:
Two tabs get opened:
https://support.mozilla.org/en-US/kb/telemetry-clientid?as=u&utm_source=inproduct
https://support.mozilla.org/en-US/products/firefox?as=u&utm_source=inproduct
Expected results:
Only one tab should be opened for https://support.mozilla.org/en-US/kb/telemetry-clientid?as=u&utm_source=inproduct
| Assignee | ||
Comment 1•2 years ago
|
||
This is the link that has the issue
| Assignee | ||
Updated•2 years ago
|
| Assignee | ||
Updated•2 years ago
|
Comment 2•2 years ago
|
||
:ebilitenelson, since you are the author of the regressor, bug 1820209, could you take a look?
For more information, please visit BugBot documentation.
Updated•2 years ago
|
Hello, thank you for the bug report!
Managed to reproduce on:
- Nightly 114.0a1;
- Firefox 113.0;
Tested and reproduced on:
- macOS 12;
- Windows 10;
- Ubuntu 22;
Setting as NEW.
Updated•2 years ago
|
Updated•2 years ago
|
Comment 4•2 years ago
|
||
Set release status flags based on info from the regressing bug 1820209
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 5•2 years ago
|
||
Clear a needinfo that is pending on an inactive user.
Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 6•1 year ago
|
||
This prevents two tabs from being opened.
Updated•1 year ago
|
Comment 8•1 year ago
|
||
| bugherder | ||
Updated•1 year ago
|
Comment 9•1 year ago
|
||
Reproduced the issue with Firefox 114.0a1 (2023-04-30) on macOS 14.
The issue is verified fixed with Firefox 131.0a1 (20240807215007) and Firefox 130.0b2 (20240807091924) on MacOS 14 ARM, Ubuntu 22 and Windows 10.
Updated•1 year ago
|
Description
•