Closed Bug 1905119 Opened 1 year ago Closed 1 year ago

[Experiment] The UI elements of the Cookie Banner Reduction CFR message are wrongly displayed for RTL builds

Categories

(Firefox :: Messaging System, defect, P1)

Firefox 128
Desktop
All
defect

Tracking

()

VERIFIED FIXED
130 Branch
Iteration:
130.1 - Jul 8 - Jul 19
Tracking Status
firefox128 --- disabled
firefox129 --- disabled
firefox130 --- verified

People

(Reporter: cfat, Assigned: aminomancer)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Attached image CFR CBB.jpg

[Affected versions]:

  • Firefox Beta 128.0b8 - Build ID: 20240626091446

[Affected Platforms]:

  • Windows 10 x64
  • macOS 12.4
  • Linux Ubuntu 20.04 x64

[Prerequisites]:

  • Have a Firefox RTL build installed (ar, he, fa, etc).
  • Have the following pref set:
    nimbus.debug = true

[Steps to reproduce]:

  1. Open the browser from the prerequisites.
  2. Copy and paste the following link in order to force enroll in the “CBB ROW Hold-back with Promo” experiment: about:studies?optin_slug=cbb-row-hold-back-with-promo&optin_branch=treatment-a&optin_collection=nimbus-preview
  3. Restart the browser.
  4. Open a new Private Window.
  5. Navigate to a website that contains a cookie banner. (e.g. bloomberg.com, cnn.com)
  6. Observe the CFR message.

[Expected result]:

  • The elements of the CFR message are correctly displayed respecting the RTL rules.

[Actual result]:

  • The message’s arrow points to the Address Bar instead of being anchored to the "Tracking Protections" button.
  • The X button, cookie icon, link, and text from the message's content are displayed in the same way as on the LTR builds.
  • The X button overlaps part of the text from the message’s content.

[Notes]:

  • Attached is a screenshot of the issue on 3 RTL builds (ar, he, fa, etc).
  • This issue is probably reproducible with other RTL builds.

Hi DJ, I think you own this CFR?

Flags: needinfo?(dwalker)

This message has custom margins that are likely responsible, so this may not be an issue with feature callouts in general.

(In reply to Shane Hughes [:aminomancer] from comment #1)

Hi DJ, I think you own this CFR?

I recall working on this a while ago. We had to do these margin adjustments due to limitations in the feature callout template that weren't compatible with the doorhanger design. I think it would be best to either modify the feature callout to accomodate the UX needs, or re-evaluate the UX here to fall more in line with the existing messaging surfaces.

Flags: needinfo?(dwalker)
Assignee: nobody → shughes
Status: NEW → ASSIGNED
Iteration: --- → 130.1 - Jul 8 - Jul 19
Priority: -- → P1
Flags: needinfo?(shughes)
Flags: needinfo?(shughes)
Pushed by shughes@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/fa7ed837efc1 Fix feature callout RTL display. r=omc-reviewers,negin
Status: ASSIGNED → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 130 Branch

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

The patch landed in nightly and beta is affected.
:aminomancer, is this bug important enough to require an uplift?

  • If yes, please nominate the patch for beta approval.
  • If no, please set status-firefox129 to wontfix.

For more information, please visit BugBot documentation.

Flags: needinfo?(shughes)

I have verified this issue on Firefox Nightly 130.0a1 (Build ID: 20240718214749) on Windows 10 x64, Ubuntu 20.04 x64, and macOS 14.4.1.

  • The message’s arrow points to the "Tracking Protections" button.
  • The X button, cookie icon, link, and text from the message's content mirror the LTR builds.
  • The X button doesn’t overlap part of the text from the message’s content.

@Shane, we noticed that on the "ar" and "fa" builds, the text within the message is not translated accordingly (the strings are in English). Could it be because on Nightly there are no translations available for these locales?

(In reply to Carmen Fat [:cfat] - Ecosystem QA from comment #10)

@Shane, we noticed that on the "ar" and "fa" builds, the text within the message is not translated accordingly (the strings are in English). Could it be because on Nightly there are no translations available for these locales?

I think that's right. Here are the current translations, and I don't see ar or fa. Looks like there are others missing as well. I don't know when the planned launch is for this message or what locales it's targeting though.

Flags: needinfo?(shughes)
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: