2026595 - The Memories toggle button is displayed as ON after we Disable both preferences from Smart Window Settings

Status: RESOLVED WONTFIX

(Core :: Machine Learning: Frontend, defect)

Description

[Rares Doghi, Desktop QA]

Found in

• 151.0a1 (2026-03-25)

Affected versions

• 151.0a1 (2026-03-25)

Affected platforms

• all

Steps to reproduce

1. Open a Smart Window.
2. Reach about:preferences#personalizeSmartWindow
3. Make sure you have a few memories saved.
4. Disable both preferences related to memories.
5. Open a new Tab.

Expected result

• When both preferences are turned off, the Memories toggle button should be crossed off. If there are no memories available the button should not be displayed at all

Actual result

• The user can disable both Memories related preferences but the button is still displayed as ON on new tab or in the sidebar.

Regression range
N/A

Comment 1

[laustin]

Rares to recheck on whether this is UX alone or if memories are still applied here.

Comment 2

[Rares Doghi, Desktop QA]

Rechecked and If the Memories toggle button is enabled they are indeed applied.

Comment 3

[Punam Dahiya [:pdahiya]]

With fix of https://mozilla-hub.atlassian.net/browse/GENAI-3669 this was implemented as part of flow captured in figma here

• Both pref on - show
• Both pref off and memory exist - show
• Both pref off and memory doesn’t exist - hide

Memory icon is shown on UI till memories are deleted. Product to review this improvement in settings as discussed in slack thread here

Comment 4

[Nick]

Attachment: Bug 2026595 - The Memories toggle button is displayed as ON after we Disable both preferences from Smart Window Settings r=pdahiya

Comment 5

[Nick]

Bug https://bugzilla.mozilla.org/show_bug.cgi?id=2026595  is not valid and will be closed - Even if both “memory generation” prefs are turned off, any existing stored memories can still be used. Those prefs control collecting/creating memories, not whether stored memories are applied. Since the Smartbar Memories button reflects usage, it should remain On in this scenario (memories are still being used; they’re just not being newly created).