2026173 - The Memories button state is not remembered when switching tabs

Status: VERIFIED FIXED

(Core :: Machine Learning: Frontend, defect)

Description

[Rares Doghi, Desktop QA]

Attachment: crossed.mp4

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. Have 2 tabs with websites opened.
3. Open the Ask sidebar for one of the tabs and Disable the Memories from the Memories button.
4. Switch between tabs.

Expected result

• The Tab where the Memories were crossed off should still be crossed off when the user returns to that tab.

Actual result

• The Memories are turned on each time a user opens or comes back to the tab.

Regression range
N/A

Comment 1

[Punam Dahiya [:pdahiya]]

Memory toggle state not remembered for tab that has no user conversation is a known issue . Will bring it up with UX for desired flow here. Thanks

Comment 2

[laustin]

This is not just the toggle/UX; Memories are applied in conversations impacted.

Comment 3

[:Gijs (he/him)]

(In reply to Punam Dahiya [:pdahiya] from comment #1)

Memory toggle state not remembered for tab that has no user conversation is a known issue . Will bring it up with UX for desired flow here. Thanks

Based on this, does it work correctly if there are conversations with at least 1 message in each chat, Rares? comment #2 makes me think it might not...

Comment 4

[Rares Doghi, Desktop QA]

Attachment: ShoeBrands.mp4

This issue occurs for the tabs where there is at least 1 conversation already started, disabling the Memories, going away and coming back to the tab, will still show the Memories as ON, and they are still being used for the next prompt.

Comment 5

[Punam Dahiya [:pdahiya]]

(In reply to :Gijs (he/him) from comment #3)

(In reply to Punam Dahiya [:pdahiya] from comment #1)

Memory toggle state not remembered for tab that has no user conversation is a known issue . Will bring it up with UX for desired flow here. Thanks

Based on this, does it work correctly if there are conversations with at least 1 message in each chat, Rares? comment #2 makes me think it might not...

My comment #2 should have been 'Memory toggle state not remembered for tab that has no last user conversation with memory disabled is a known issue' . Video in comment #4 has last conversation message in the tab with memory enabled and that got used to decide memory toggle state on switching back to that tab.

Based off UX feedback we want to fix this by capturing toggle state at tab level. Possible it will be a uplift candidate, will start thread in slack on decision around that

Comment 6

[Nick]

Attachment: Bug 2026173 - The Memories button state is not remembered when switching tabs r=omarg

Comment 7

[Pulsebot]

Pushed by [e-mail]:
https://github.com/mozilla-firefox/firefox/commit/fe476a04868c
https://hg.mozilla.org/integration/autoland/rev/7dd7e6cd555f
The Memories button state is not remembered when switching tabs r=omarg,ai-frontend-reviewers

Comment 8

[amarc]

https://hg.mozilla.org/mozilla-central/rev/7dd7e6cd555f

Comment 9

[Rares Doghi, Desktop QA]

This issue is Verified as fixed in our latest Nightly 151.0a1 (2026-04-15)

Comment 10

[BugBot [:suhaib / :marco]]

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

• If yes, please nominate the patch for beta approval.
  • See https://wiki.mozilla.org/Release_Management/Requesting_an_Uplift for documentation on how to request an uplift.
• If no, please set status-firefox150 to wontfix.

For more information, please visit BugBot documentation.

Comment 11

[Punam Dahiya [:pdahiya]]

Just wanted to note fix landed in patch ensures memory toggle tab state is retained when there is at least one message on tab which is reasonable.

Original description #comment 0 of this bug points at tab state is not retained when there is no message (known behavior) and different from #comment 4

Comment 12

[Rares Doghi, Desktop QA]

Updating the main status flag.