Skip to content
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

Closed
ppittle opened this issue Jul 8, 2020 · 5 comments · Fixed by brave/brave-core#8626
Closed

Search Engines added by Extensions unavailable in Private Window #10601

ppittle opened this issue Jul 8, 2020 · 5 comments · Fixed by brave/brave-core#8626

Comments

@ppittle
Copy link

ppittle commented Jul 8, 2020

Description

Search Engines added by Extensions can't be referenced by Keyword + Tab in Private Window

image

Given the user has installed an Extension which adds a Search Engine
And the user has modified the Extension so that "Allow in private" is true.

Given the user is in a Private Window
And the Address Bar has Focus
When the user types the Extension's Search Keyword and presses Tab

Then further input is directed to the Extension's Search Engine

Scenario fails for Private Window:
image

Works with a 'normal' Window:

image

Steps to Reproduce

  1. Install an Extension that Provides a Search Engine. I used LastPass

brave://settings/searchEngines

image

  1. Ensure the Extension is available in Private

brave://extensions/?id=hdokiejnpimakedhajhdlcegeplioahd

image

  1. Open a new Private Window
  2. Focus the Address Bar
  3. Type the Extension's Search Engine Keyword and press Tab. (In the case of LastPass, it's lp)

Actual result:

image

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

image

Reproduces how often:

Always reproduces

Brave version (brave://version info)


Brave | 1.10.97 Chromium: 83.0.4103.116 (Official Build) (64-bit)
-- | --
Revision | 8f0c18b4dca9b6699eb629be0f51810c24fb6428-refs/branch-heads/4103@{#716}
OS | Windows 10 OS Version 1909 (Build 18363.900)

Version/Channel Information:

  • Can you reproduce this issue with the current release? YES
  • Can you reproduce this issue with the beta channel?
  • Can you reproduce this issue with the dev channel?
  • Can you reproduce this issue with the nightly channel?

Other Additional Information:

  • Does the issue resolve itself when disabling Brave Shields? NO
  • Does the issue resolve itself when disabling Brave Rewards? NO
  • Is the issue reproducible on the latest version of Chrome? NO

image

Miscellaneous Information:

@atahabaki
Copy link

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.

@rebron rebron added the priority/P5 Not scheduled. Don't anticipate work on this any time soon. label Sep 1, 2020
@bsclifton
Copy link
Member

Related (or possible duplicate of) #10549

@ppittle
Copy link
Author

ppittle commented Nov 5, 2020

Agree this and #10549 appear to be the same root issue. But I will point out, mine has more pictures :D

@bsclifton bsclifton added priority/P4 Planned work. We expect to get to it "soon". and removed priority/P5 Not scheduled. Don't anticipate work on this any time soon. labels Apr 12, 2021
simonhong added a commit to brave/brave-core that referenced this issue Apr 17, 2021
fix: brave/brave-browser#15224
fix: brave/brave-browser#10601
fix: brave/brave-browser#14218

Changed to use same TemplateURLService for normal & private profile.
simonhong added a commit to brave/brave-core that referenced this issue Apr 19, 2021
fix: brave/brave-browser#15224
fix: brave/brave-browser#10601
fix: brave/brave-browser#14218

Changed to use same TemplateURLService for normal & private profile.
simonhong added a commit to brave/brave-core that referenced this issue Apr 22, 2021
fix: brave/brave-browser#15224
fix: brave/brave-browser#10601
fix: brave/brave-browser#14218

Changed to use same TemplateURLService for normal & private profile.
simonhong added a commit to brave/brave-core that referenced this issue Apr 30, 2021
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.
simonhong added a commit to brave/brave-core that referenced this issue May 7, 2021
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.
simonhong added a commit to brave/brave-core that referenced this issue May 10, 2021
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.
@simonhong simonhong added this to the 1.26.x - Nightly milestone May 14, 2021
@stephendonner
Copy link

stephendonner commented May 17, 2021

Verified PASSED using the testplan from brave/brave-core#8626 with build

Brave 1.26.22 Chromium: 91.0.4472.57 (Official Build) nightly (x86_64)
Revision e3443317fa07f1e9997e4a9c738eddfefc3c0292-refs/branch-heads/4472_54@{#6}
OS macOS Version 11.3.1 (Build 20E241)

Steps:

  1. clean profile, launched Brave
  2. installed Ecosia extension - https://chrome.google.com/webstore/detail/ecosia-the-search-engine/eedlgdlajadkbbjoobobefphmfkcchfk/related
  3. confirmed Normal window's default search provider is ecosia
  4. opened private window and confirmed ecosia is default search provider
  5. toggled DDG button to On and confirmed it doesn't change the search provider - still using Ecosia
  6. toggled DDG button to Off and confirmed it doesn't change the search provider - still using Ecosia
  7. in brave://extensions, on the Ecosia extension details page, I toggled Allow in private on and off
  8. confirmed changing Allow in private option doesn't affect private window's search provider - still using Ecosia
  9. disabled Ecosia extension and check normal and private windows use default search provider - uses Google
  10. toggled DDG button to On in Private and confirmed search provider is changed to DuckDuckGo
steps 1-2 step 3 step 4 step 5 step 6 step 7 step 8 step 9 step 10
Screen Shot 2021-05-17 at 3 56 37 PM Screen Shot 2021-05-17 at 3 57 28 PM Screen Shot 2021-05-17 at 3 57 45 PM Screen Shot 2021-05-17 at 3 58 12 PM Screen Shot 2021-05-17 at 3 58 23 PM Screen Shot 2021-05-17 at 4 03 18 PM Screen Shot 2021-05-17 at 4 04 19 PM Screen Shot 2021-05-17 at 4 04 36 PM Screen Shot 2021-05-17 at 4 04 59 PM

Verification passed on


<!--StartFragment-->
Brave | 1.26.47 Chromium: 91.0.4472.77&nbsp;(Official Build)&nbsp;beta&nbsp;(64-bit)
-- | --
Revision | 1cecd5c8a856bc2a5adda436e7b84d8d21b339b6-refs/branch-heads/4472@{#1246}
OS | Windows&nbsp;10 OS Version 2004 (Build 19041.985)

<!--EndFragment-->

example example example example example example example example example example example example example
image image image image image image image image image image image image image

Verification passed on

Brave 1.26.45 Chromium: 91.0.4472.77 (Official Build) beta (64-bit)
Revision 1cecd5c8a856bc2a5adda436e7b84d8d21b339b6-refs/branch-heads/4472@{#1246}
OS Ubuntu 18.04 LTS

Extension was unable to change default search engine in Normal Window nor Private Window. Logged #16227

@rebron rebron changed the title [Desktop] Search Engines added by Extensions unavailable in Private Window Search Engines added by Extensions unavailable in Private Window Jun 21, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment