Fix get_page_content to not return chrome:// error that the assistant doesn't know what to do with
Categories
(Core :: Machine Learning: Frontend, defect, P1)
Tracking
()
People
(Reporter: rdoghi, Assigned: tliu, NeedInfo)
References
(Blocks 1 open bug)
Details
(Whiteboard: [genai][models][qa])
Attachments
(2 files)
Found in
- Nightly 150.0a1 (2026-02-24)
Affected versions
- Nightly 150.0a1 (2026-02-24)
Beta 149.0b1
Affected platforms
- all
Preconditions
Have the Gemini AI model selected.
Steps to reproduce
- Open a Smart window.
- Type Hi or Hello in the Smart bar.
Expected result
- The Ai model should respond appropriately to the users Prompt.
Actual result
- The Gemini AI model is returning an Error about not being able to access the content from the New tab.
Regression range
N/A
Updated•6 months ago
|
Updated•6 months ago
|
Updated•6 months ago
|
| Assignee | ||
Updated•6 months ago
|
| Assignee | ||
Comment 1•6 months ago
|
||
Quick update:
While reproducing this issue, I found that get_page_content is not used so it's not the root cause.
Also, there is another bug that partially impacts on this one. I'll fix that one first, and then we should get less unwanted response.
Even with that fix, some test cases like query = "h" still failed though not mentioning "Chrome" anymore:
I can't access the content of the New Tab page. Is there anything else I can help you with?
To address/mitigate this issue I would need to tune prompts and some evaluations are needed to see if the change caused regression in other aspects.
| Assignee | ||
Comment 2•6 months ago
|
||
Update:
verified the other bug is irrelevant to this one, the "improvement" should due to randomness of LLM.
It would still need some prompt tuning to mitigate this issue.
Updated•5 months ago
|
Comment 3•5 months ago
|
||
The severity field is not set for this bug.
:Mardak, could you have a look please?
For more information, please visit BugBot documentation.
Updated•5 months ago
|
| Assignee | ||
Comment 4•5 months ago
|
||
Comment 6•5 months ago
|
||
| bugherder | ||
| Reporter | ||
Comment 7•5 months ago
|
||
Verified as fixed in our latest Nightly Build 150.0a1 (2026-03-18) we can reopen this issue if it starts to show up for other prompts
Description
•