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
Updated default search providers in KR #10590
Conversation
061226d
to
3161ace
Compare
android/java/org/chromium/chrome/browser/onboarding/SearchEngineEnum.java
Outdated
Show resolved
Hide resolved
3161ace
to
df6917f
Compare
@rebron @bradleyrichter Do we want to update Android onboarding with this default search provider change? |
@timchilds @anthonypkeane We need getting assets for Daum and Naver, logo and description. |
We don't show this screen in Android during onboarding. If we are, it is a bug. |
@anthonypkeane This search provider onboarding is launched for first touch on omnibox. |
|
Kindly ping for logo and description :) |
@rmcfadden3 can you please help with the copy for Daum & Naver? |
How about these descriptions?
I could try to add more to differentiate them, but character count is really limited. LMK. |
Hi @simonhong Does this work ok? Thanks |
@anthonypkeane Desc seems fine. and I was also waiting both providers' logo icon. |
df6917f
to
68e4b7d
Compare
|
68e4b7d
to
f8f14e7
Compare
|
|
1 similar comment
|
f8f14e7
to
2204ec2
Compare
|
2204ec2
to
f60a04b
Compare
|
f60a04b
to
ea40ee5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Android changes LGTM
@simonhong were you able to verify the change for android on device ? |
Yes, above screenshots came from my android phone. |
ea40ee5
to
25bf853
Compare
fix brave/brave-browser#18855 Default search provider list will include Brave Search, Naver, Daum and Google. And Naver will be set as a default provider.
Daum & Naver are listed in search provider list
25bf853
to
873c691
Compare
@@ -81,6 +81,13 @@ const std::vector<BravePrepopulatedEngineID> brave_engines_AU_IE = { | |||
PREPOPULATED_ENGINE_ID_ECOSIA, | |||
}; | |||
|
|||
const std::vector<BravePrepopulatedEngineID> brave_engines_KR = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wonder why these are vectors instead of plain arrays?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, I'll try to handle this as a f/u. Filed brave/brave-browser#27943
Updated default search providers in KR
Verification PASSED on
|
Example |
Example |
Example |
Example |
Example |
Example |
---|---|---|---|---|---|
Test Case #2
- Upgrade from 1.49.55 Chromium: 109.0.5414.86
--> 1.49.82 Chromium: 110.0.5481.52
Verification FAILED on Pixel 6
running Android 13
using the following build(s):
Brave | 1.49.82 Chromium: 110.0.5481.52 (Official Build) canary (32-bit)
--- | ---
Revision | 979113183ded4544a2c443aceb1629c430907e52-refs/branch-heads/5481@{#636}
OS | Android 13; Build/TQ1A.230105.002
Test Case #1
- Clean Profile
- installed
1.49.82 Chromium: 110.0.5481.52
and ensured that the SE onboarding is displayed when tapping on omnibox - ensured that the new SE mentioned via Updated default search providers in KR #10590 (comment) are being displayed
- ensured that
Naver
is selected as the default SE via the SE onboarding - ensured that you can switch to different SE via
Hamburger Menu
->Search engines
without any issues - ensured that users choice is being retained when restarting the browser
Example |
Example |
Example |
Example |
---|---|---|---|
Test Case #2
- Upgrade from 1.49.55 Chromium: 109.0.5414.86
--> 1.49.82 Chromium: 110.0.5481.52
Test Case #1
- Default SE (Google) selected via omnibox search onboarding
- installed
1.49.55 Chromium: 109.0.5414.86
and ensured that the previous onboarding appeared once tapping on omnibox - ensured that
Google
was selected as the default SE via the search onboarding and continued withGoogle
selected - ensured that
Google
was selected as the default SE for bothStandard Tab
&Private Tab
Example |
Example |
Example |
Example |
---|---|---|---|
- upgraded from
1.49.55 Chromium: 109.0.5414.86
-->1.49.82 Chromium: 110.0.5481.52
- ensured that
Google
was still set as the default SE for bothStandard Tab
&Private Tab
- ensured that the new SE are being displayed within
Standard Tab
&Private Tab
- ensured that
Google
is also being displayed via bothStandard Tab
&Private Tab
- ensured that
Brave
is at the top of the list for bothStandard Tab
&Private Tab
- ensured that you can switch to other SE after upgrading without any issues
- ensured that the changes are retained when restarting the browser several times
Example |
Example |
Example |
---|---|---|
Test Case #2
- Selecting other SE (DDG) via omnibox search onboarding
- installed
1.49.55 Chromium: 109.0.5414.86
and ensured that the previous onboarding appeared once tapping on omnibox - ensured that
Google
was selected as the default SE via the search onboarding - select
DDG
as the default SE and ensure bothStandard Tab
&Private Tab
are usingDDG
Example |
Example |
Example |
Example |
---|---|---|---|
- upgraded from
1.49.55 Chromium: 109.0.5414.86
-->1.49.82 Chromium: 110.0.5481.52
- ensured that
DDG
was still set as the default SE for bothStandard Tab
&Private Tab
- ensured that the new SE are being displayed within
Standard Tab
&Private Tab
- ensured that
DDG
is also being displayed via bothStandard Tab
&Private Tab
- ensured that
Brave
is at the top of the list for bothStandard Tab
&Private Tab
- ensured that you can switch to other SE after upgrading without any issues
- ensured that the changes are retained when restarting the browser several times
Example |
Example |
Example |
---|---|---|
Test Case #3
- Selecting two different SE via Search Settings
before upgrading
- installed
1.49.55 Chromium: 109.0.5414.86
and ensured that the previous onboarding appeared once tapping on omnibox - ensured that
Google
was selected as the default SE via the search onboarding - select
Startpage
as the default SE and ensure bothStandard Tab
&Private Tab
are usingStartpage
- changed the default SE for both
Standard Tab
(Bing) &Private Tab
(Qwant)
Example |
Example |
Example |
Example |
Example |
---|---|---|---|---|
- upgraded from
1.49.55 Chromium: 109.0.5414.86
-->1.49.82 Chromium: 110.0.5481.52
- ensured that
Bing
was still set as the default SE forStandard Tab
- ensured that
Qwant
was still set as the default SE forPrivate Tab
- ensured that the SE are being displayed/selected within
Standard Tab
&Private Tab
- ensured that
Brave
is at the top of the list for bothStandard Tab
&Private Tab
- ensured that you can switch to other SE after upgrading without any issues
- ensured that the changes are retained when restarting the browser several times
Example |
Example |
Example |
---|---|---|
Created brave/brave-browser#28232 which should be fixed on Also found brave/brave-browser#28262 which isn't related to the above. |
fix brave/brave-browser#18855 fix brave/brave-browser#28232 fix brave/brave-browser#28235 Original PR(#10590) was reverted because it revealed another two bugs(#28232, #28235). As fixes for both bugs were merged, we can reland SK's default list.
Resolves brave/brave-browser#18855
Desktop & android will have Brave Search, Daum, Naver and Google as a default search provider.
Desktop search engine settings page
Android onboarding page
Android search engine settings page
Submitter Checklist:
QA/Yes
orQA/No
;release-notes/include
orrelease-notes/exclude
;OS/...
) to the associated issuenpm run test -- brave_browser_tests
,npm run test -- brave_unit_tests
,npm run lint
,npm run gn_check
,npm run tslint
git rebase master
(if needed)Reviewer Checklist:
gn
After-merge Checklist:
changes has landed on
Test Plan: