1824998 - TCP CFR behaves incorrectly after the changes made in 1819473

Status: VERIFIED FIXED

(Firefox for Android :: Privacy, defect, P1)

Description

[Delia Pop (Android QA)]

Attachment: TCP_CFR.mp4

Steps to reproduce

1. Install and launch Firefox Nightly 113.0a1 from 03/27-28.
2. Visit a webpage.
3. Observe if the Total Cookie Protection CFR is displayed.
4. Once the CFR is displayed, tap the "Learn about Total Cookie Protection" link.
5. Observe the SUMO page opened and the URL.

Expected behavior

In Step 3, the Total Cookie Protection CFR is displayed right after accessing a webpage the first time.
In Step 5, the https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-android page is opened.

Actual behavior

In Step 3, the Total Cookie Protection CFR is only displayed after repeatedly accessing the webpage or performing at least 2 searches.
In Step 5, a "page not found" error page is opened, with the following URL: https://support.mozilla.org/1/mobile/113.0a1/Android/en-US/enhanced-tracking-protection-firefox-android

Device information

• Firefox version: latest Nightly 113.0a1 from 03/27 and 03/28
• Android device model: Google Pixel 6 (reproducible with other devices)
• Android OS version: Android 13

Any additional information?

The behavior was observed while testing https://bugzilla.mozilla.org/show_bug.cgi?id=1819473 .

Comment 1

[Delia Pop (Android QA)]

Attachment: TCP_CFR_logcat.txt

Attaching a logcat for the behavior described above.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

:avirvara, since you are the author of the regressor, bug 1819473, could you take a look?

For more information, please visit auto_nag documentation.

Comment 3

[Chris Peterson [:cpeterson]]

[Tracking Requested - why for this release]:

This bug is important to fix in 113 before it reaches Release. It's a regression in Nightly 113 that breaks both the TCP notification popup and its SUMO article link.

Comment 4

[Mihai Adrian Carare [:mcarare]]

From the discussion in the original ticket (GitHub), it seems that the link change was unnecessary.

But I would like to point out that the popup behavior is in no way related to the link, so if there is a regression in that behavior, it is not caused by the link update.

Comment 5

[BMO Github Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1824998 - revert commit for Bug 1819473 (#1456)

Comment 6

[BMO Github Automation]

Attachment: [mozilla-mobile/firefox-android] Bug 1824998 - Revert changes from Bug 1819473 (#1461)

Comment 7

[BMO Github Automation]

Authored by https://github.com/Alexandra-Virvara
https://github.com/mozilla-mobile/firefox-android/commit/ece59cb6262da37604f3bfb77b7a9ef7d7d9f497
[main] Bug 1824998 - Revert changes from Bug 1819473

Comment 8

[Delia Pop (Android QA)]

Verified as fixed on the latest Nightly 113.0a1 from 03/30. The https://support.mozilla.org/en-US/kb/enhanced-tracking-protection-firefox-android?as=u&utm_source=inproduct ULR opens the SUMO page and the content is available.
I noticed that although the previous change was reverted, the "enhanced-tracking-protection-firefox-android" string is still displayed in the URL and that it was already available in previous Nightly builds before the change.
A separate ticket will be opened to handle the other issue with the TCP CFR not being displayed right after accessing a webpage the first time.

Tested with the following devices:

• Samsung Galaxy A53 5G (Android 13)
• Xiaomi 12 Pro (Android 13)
• OPPO A15s (Android 10)