Unable to test the issue from TE end as we are not able to find Baidu search engine from default search engine suggestions. Hence adding appropriate component for further triage.

Tried with the below steps and could not reproduce the issue

Steps Followed:
1. Launched Browser
2. Navigated to www.baidu.com
3. Searched xiangji
4. No page reload is seen.

@UI>Browser>Mobile>SearchWidget team: Please take a look at this issue and help us in addressing the issue.

Thanks!!

Normally a search engine gets into the Chrome settings ("recently visited" section) by publishing an open search description document (http://www.opensearch.org/Home).  You can see duckduckgo.com do this.  I can't seem to get baidu.com to do this (though there may be an option somewhere I can't find because I can't read the Chinese and translate doesn't offer to translate the Baidu settings page).

xfzhang632@ how did you get Baidu added to your default search engine list?  I suspect there's either a problem with the OS document they publish, or in Chrome's handling of it.

When I visit Baidu.com in Firefox for Android and long press the search field, I do get the 'add search engine' option but I don't know for sure that's using the same OpenSearch mechanism Chrome does.

sandeepkumars@, rbyers@, thanks a lot for you verification. I can't upload video, sorry for any inconvenience.

I just know that it's indeed no baidu search engine in the Chrome Settings when the system language is English before installing Chrome apk, however, if set system language to Chinese, and then install the Chrome, there should be baidu search engine. 

I found there are three ways to reproduce.
1) Just install the Chrome for android and load the url "https://www.baidu.com/s?word=xiangji". 

I downloaded Chrome apk from https://www.androidapksfree.com/apk/chrome-browser-apk-latest-version-download/, but I think the other source is ok.

2). I even can reproduce the issue in desktop chrome with "Developer tools" open. The steps are:
 -- Clear the browser cache.
 -- Open "https://www.baidu.com/s?word=xiangji" in desktop chrome.
 -- Open "Developer tools" by enter F12 or "Ctrl+Shift+I"
 -- Change to left top button "Responsive" to "Galaxy S5" or other Android phone emulator.
 -- Reload the page, you will see the page constantly reload now, and the url will become to "https://www.baidu.com/s?word=xiangji&bd_ck=0", to https://www.baidu.com/s?word=xiangji&bd_ck=0&bd_ck=0, to https://www.baidu.com/s?word=xiangji&bd_ck=0&bd_ck=0&bd_ck=0......
with every time reloading, one more "&bd_ck=0" is added.

3) The steps:
  -- Must firstly to change the Android phone system language to Chinese(Simple).
  -- Install the Android Chrome apk, https://www.androidapksfree.com/apk/chrome-browser-apk-latest-version-download/
  -- In Chrome Settings (Chinese is "设置")，change the search engine (Chinese is "搜索引擎") to "baidu.com".

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Hi, any update on this? Thanks :-)

I suspect there's problem with the URL used by default on Baidu.  It's here:
https://cs.chromium.org/chromium/src/out/Debug/gen/components/search_engines/prepopulated_engines.cc?sq=package:chromium&l=238-257
The URL is "https://www.baidu.com/#ie={inputEncoding}&wd={searchTerms}"

(For what it's worth, this URL differs from the URL used in the demonstration in comment #4.)

xfzhang632@, since you see technically capable (you checked firefox already), could you let us know what URL that firefox is fetching first.  (Not after redirects or anything, the first URL they fetch.)  Maybe we could revise the URL to theirs.

I think this is likely something Baidu could fix on their end too.

explicit CC pkasting@, as he usually manages this list

Friendly Ping!!

Is there any recent updates available on this issue?

Thanks!!

As comment 8 notes, the URL in our source tree isn't the same as that in comment 4.  Comment 4 talks about "/s?word=", and comment 8 "/#wd=".  So the first thing to check would be if this happens when using our current URL.  I wonder if this is an artifact of where/how the APK was obtained?

I also can't reproduce the bug described using the steps in comment 4.  In my case the page did reload some (so I wound up with two &bd_ck=0 params), but then stopped.  So another thing to check would be whether this still happens for the reporter (maybe Baidu added a fix)?

This issue should be caused by the url, not chrome bug, so I think it can be closed. Thanks all.

Are you saying that if you follow the steps in comment 0 now, you get a different search URL that doesn't cause infinite reloading?

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

pkasting@, no, I still can reproduce the problem, but I means I am sure the infinite reloading issue is caused by the url of baidu search generated.

Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Officially assigning to pkasting@, as he's the one who's most involved in discussions about how to fix this or close this.

I'm still not fully clear on what's going on.

I'm not too worried about whether manually inputting a particular URL causes Baidu to infinitiely reload -- that's Baidu's issue.

I'm more worried about whether searches in the omnibox using the built-in Baidu provider generate URLs that cause Baidu to infinitely reload.  We should use URLs that don't do that.

AFAICT from the comments above/my own tests, the URLs we generate should not cause infinite reloads today, in which case this seems safe to close.  But if it's possible to reproduce this without typing in any manual URLs, just by setting the omnibox search provider to Baidu and doing a search, please say that -- we need to take action then.