-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenSearch not properly picking up search suggestion API #537
Comments
https://cdn.search.brave.com/serp/v2/_app/immutable/assets/opensearch.8acac4ab.xml this is the manifest of brave search:
this the excerpt from preferences:
|
I am checking, it seems that the https call to the manifest is being blocked. |
so, the problem is context.
in this case corb (orb in chromium) intervenes to block the request, since the header marks the xml result as nosniff, resulting in one of corb's blocking rules https://github.com/annevk/orb#orbs-algorithm being the initiator of a different origin |
but in any case the request is not resolved, and would be permanently solved if the user could change those values. |
Preliminary checklist
Can the bug be reproduced with corresponding Chromium version?
Yes
Cromite version
119.0.6045.160
Device architecture
arm64
Platform version
Android 13
Android Device model
SM-A426UI\DS
Is the device rooted?
No
Changed flags
No flags changed
Is this bug happening in an incognito tab?
Yes
Is this bug caused by the adblocker?
No
Is this bug a crash?
No
Describe the bug
No search suggestions, either using Google or using Brave Search. I tested in Chromium. Google search suggestions worked fine. Brave Search suggestions didn't work.
So one part is that Google search suggestions don't work.
The other part is that Brave's suggestions don't work, here or in Chromium. Firefox has a field where you can add an address to query for search suggestions.
On Firefox, adding either
https://google.com/complete/search?client=firefox&q=%s
orhttps://search.brave.com/api/suggest?q=%s
proved to be sufficient.Both of these addresses are provided in the OpenSearch data for each respective page, so it seems Chromite is simply not picking it up correctly.
Steps to reproduce the bug
Expected behavior
There are search suggestions
Screenshots
Details
The text was updated successfully, but these errors were encountered: