2015509 - The Smart Window TOU modal is not displayed for users that never saw the TOU modal

Status: VERIFIED FIXED

(Core :: Machine Learning: Frontend, defect, P1)

Description

[Rares Doghi, Desktop QA]

Found in

• Nightly 149.0a1 (2026-02-09)

Affected versions

• Nightly 149.0a1 (2026-02-09)

Affected platforms

• All

Steps to reproduce

1. Launch an older version of Firefox <138
2. Upgrade Firefox to our latest build.
3. Open a Smart window from the Window switcher.

Expected result

• The TOU modal should be displayed on top of the FxA page.

Actual result

• The TOU modal is not displayed and the user can reach a Smart window without accepting the Terms of use.

Regression range
N/A

Comment 1

[Ed Lee :Mardak]

punam, is there a bug for the nimbus rollout of this message? or maybe it'll be this one

Comment 2

[Punam Dahiya [:pdahiya]]

This is getting fixed and tracked with https://mozilla-hub.atlassian.net/browse/OMC-1466 . NI @sachung to help share test steps with link to Nimbus Experimenter rollout ( Fx 149, all channels) with TOS Modal for QA to test

Comment 3

[Ed Lee :Mardak]

https://experimenter.services.mozilla.com/nimbus/ai-window-tou-modal-existing-users seems to be in draft but perhaps could be copied to stage or put in preview for initial qa?

Comment 4

[Sarah Chung [:sachung]]

The Nimbus experimenter rollout is going to be abandoned and instead the ToU modal will be landed on train in Bug 2016449!

Comment 5

[Ed Lee :Mardak]

should be fixed with bug 2016449
https://hg.mozilla.org/mozilla-central/rev/2ff084209db6

Comment 6

[Rares Doghi, Desktop QA]

Hi @Ed, this issue still occurs in our latest Nightly 149.0a1 (2026-02-23), there is no point during onboarding when the TOS modal is displayed for us.

Comment 7

[Ed Lee :Mardak]

Attachment: terms prefs.png

you need to have region set to US or CA

just making sure the prefs are cleared to represent pre-tos existing users:
termsofuse.acceptedDate = 0
termsofuse.acceptedVersion = 0
termsofuse.bypassNotification = false

Comment 8

[Rares Doghi, Desktop QA]

Verified as fixed in our latest Nightly 150.0a1 (2026-02-24) and beta 149.0b1