Make implicit current-tab chip removable and prevent duplicate rendering
Categories
(Core :: Machine Learning: Frontend, enhancement)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox150 | --- | verified |
People
(Reporter: echa, Assigned: echa)
References
(Blocks 1 open bug)
Details
(Whiteboard: [genai][chat])
Attachments
(1 file)
Context chips in the user message bubble should only be shown the first time a given page is used as implicit context; subsequent messages with the same current tab should not repeat the chip visually.
Updated•5 months ago
|
Allows the implicit current-tab chip to be removed in sidebar mode by persisting dismissed state in SmartbarInput and skipping it during context resolution. Also passes contextPageUrl through commit/storage and suppresses duplicate rendering, so the chip appears only once per page unless explicitly re-added.
Updated•5 months ago
|
Comment 4•5 months ago
|
||
| bugherder | ||
Comment 5•5 months ago
|
||
Hi @echa can you give me an example for this issue ? We can now remove the context chip, however if we dont remove it from the Smart bar header, regardless of our prompts the context chip will always be displayed, for example:
I was on the IGN page asking about a review where the context chip is displayed for the current tab, however if we ask about something else in the same tab, the Context chip will still be displayed in the Smart bar header, should it be removed automatically when we change topics to something else ?
(In reply to Rares Doghi, Desktop QA from comment #5)
Hi @echa can you give me an example for this issue ? We can now remove the context chip, however if we dont remove it from the Smart bar header, regardless of our prompts the context chip will always be displayed, for example:
I was on the IGN page asking about a review where the context chip is displayed for the current tab, however if we ask about something else in the same tab, the Context chip will still be displayed in the Smart bar header, should it be removed automatically when we change topics to something else ?
no, the context chip will be there in the input box header until it is explicitly removed. The duplicate rendering behaviour is related to the context chips in the user message bubble. Steps to verify:
- Navigate to a website, example ign.com
- Verify IGN.com context chip appears in the input box header automatically
- send a message to the assistant
- Verify IGN.com context chip appears in the user message bubble header
- send another message (while still on the same page)
- verify IGN.com context chip is no longer in the header (and same for all following messages on that page)
When you navigate to another URL, the context chip should change, and again appear only once in the user message bubble. Does that make sense?
Comment 7•4 months ago
|
||
Thank you for Clearing that up, This issue is verified as fixed in our latest Nightly 150.0a1 (2026-03-10)
Description
•