-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Search Engines added by Extensions unavailable in Private Window #10601
Comments
Hi!.. I'm facing that too... I've developed a Chrome extension which uses Chromium's Omnibox API for quickly search anything, anywhere. Then uploaded it to Chrome web store which I called it "smartbox: Smart Searching". If you're interested in, you can take a look at here. It works pretty well with Google Chrome (works on incognito mode too). On Brave, it is not working. Please fix this issue. Maybe this is not an issue but. Make an exception for this to work on both private and Tor sessions too. Have a great day. |
Related (or possible duplicate of) #10549 |
Agree this and #10549 appear to be the same root issue. But I will point out, mine has more pictures :D |
fix: brave/brave-browser#15224 fix: brave/brave-browser#10601 fix: brave/brave-browser#14218 Changed to use same TemplateURLService for normal & private profile.
fix: brave/brave-browser#15224 fix: brave/brave-browser#10601 fix: brave/brave-browser#14218 Changed to use same TemplateURLService for normal & private profile.
fix: brave/brave-browser#15224 fix: brave/brave-browser#10601 fix: brave/brave-browser#14218 Changed to use same TemplateURLService for normal & private profile.
fix: brave/brave-browser#15224 fix: brave/brave-browser#10601 fix: brave/brave-browser#14218 Crash comes from absense of exension search provider data in private profile's TemplateURLService because we are using different TemplateURLService for private profile. When search provider extension is loaded/installed, browser doesn't notify about this adding to private profile's TUS. To fix this, each SearchEngineProviderService sets extension's template url data to its service when normal profile's search provider comes from extension.
fix: brave/brave-browser#15224 fix: brave/brave-browser#10601 fix: brave/brave-browser#14218 Crash comes from absense of exension search provider data in private profile's TemplateURLService because we are using different TemplateURLService for private profile. When search provider extension is loaded/installed, browser doesn't notify about this adding to private profile's TUS. To fix this, each SearchEngineProviderService sets extension's template url data to its service when normal profile's search provider comes from extension.
fix: brave/brave-browser#15224 fix: brave/brave-browser#10601 fix: brave/brave-browser#14218 Crash comes from absense of exension search provider data in private profile's TemplateURLService because we are using different TemplateURLService for private profile. When search provider extension is loaded/installed, browser doesn't notify about this adding to private profile's TUS. To fix this, each SearchEngineProviderService sets extension's template url data to its service when normal profile's search provider comes from extension.
Verified
Steps:
Verification passed on
Verification passed on
Extension was unable to change default search engine in Normal Window nor Private Window. Logged #16227 |
Testing brave/brave-core#8626 will cover the following issues: |
Description
Search Engines added by Extensions can't be referenced by Keyword + Tab in Private Window
Scenario fails for Private Window:
Works with a 'normal' Window:
Steps to Reproduce
lp
)Actual result:
Tab Cycles through the History list that appears in the Address bar. Control is not routed to the Extension's Search Engine.
Expected result:
Private Window should behave as a 'normal' Window does. Input should be routed to the Extension's Search Engine
Reproduces how often:
Always reproduces
Brave version (brave://version info)
Version/Channel Information:
Other Additional Information:
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: