The issue seems to be related to WebDriver-ChromeDriver which seems to be out of TE-scope. Hence, adding label TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!

I was able to repro this issue, but haven't found the root cause. There appears to be some interference between the JavaScript used by ChromeDriver to find an element, and the JavaScript used by the page itself. Finding an element should be a read-only operation, but it's possible that some of the JavaScript functions used by ChromeDriver have been re-defined to have side effects.

The original code for the JavaScript inside atom.cc is at https://github.com/SeleniumHQ/selenium/blob/381f815652933f7077762ffba5f18794ab88c9b5/javascript/chrome-driver/atoms.js#L332 . It uses some code from https://github.com/SeleniumHQ/selenium/tree/381f815652933f7077762ffba5f18794ab88c9b5/javascript/atoms/locators .

Thanks for pointing out the original js code, I am also trying to locate the cause, looking forward to your help in fixing.

Moreover, in 'https://www.starbucks.com/account/home' the case maybe somehow similar. Navigate to this url with chrome driver, if perform with findelement before click login button, the login button will never process successfully (if without any driver find or switchframe action, all mannually input & click login will succeed). 
But in this case there's no js exception hint in the console, notice that there's ivoation used for this login site. Could that be similar reason inside findelement js script(which may have side effects), how can I pass that though. 

@johnchen@chromium.org. I think I find the bug, and still need your help on how to locally update.

Bug reason:
In kCallFunctionScript [from 'https://github.com/PeterWangIntel/crosswalk-webdriver-python/blob/master/browser/js.py'], in function getPageCache (element_util.cc::FindElement -> WebViewImpl::CallFunction -> kCallFunctionScript), you use the document.cache key as '$cdc_asdjflasutopfhvcZLmcfl_' and reset it. This will both break the TDbank and Starbucks login page I mentioned above. I mean, if you change this key to another one, everything work well. So I think your people copy this key from some public lib that others can also shared this key to do their page cache? 

Then I need your help on how to locally make it work. 
As the 'kCallFunctionScript' I can only google to find it in that js.py file, but can not find in git download chromium project? how can I update this file and try locally? 

is it chrome/test/chromedriver/js/call_function.js will replace kCallFunctionScript ? 

Locally try randomly set another key will solve.
Still confused about how kCallFunctionScript been compiled from call_function.js ? 

And another question, as I use 'ninja -C out/Release chromedriver' to locally build, it turns out to be a large folder (dll, libs there, seems there should be some command to build a release version?). How can I bundle them all to only one chromedriver.exe?

@johnchen Any updates?

Summarize below questions.
1. any args for command 'ninja -c out/Release chromedriver' to build a release(clean) version of driver.exe (same as what we downloaded from https://chromedriver.storage.googleapis.com/index.html?path=2.40/) ?

2. how chrome/test/chromedriver/js/call_function.js get applied to 'kCallFunctionScript' in WebViewImpl::CallFunction ?

3. As locally build driver using 'ninja -C out/Release chromedriver', based on branch master or tag such as 67.XX(should be chrome version) without any code change, the builded driver.exe acts not exactly as what I downloaded (try call selenium execute script, specific sites such as ally will fail as httpcommandexcutor cannot get response from url such as /session/sessionid/excute, socket forcily closed.)
How can I get the exactly same code version(which tag or which branch should I checkout) of chromedriver.exe 2.40/2.39, and build based on that one?
 

@johnchen@chromium.org Looking forward to your reply on above 3 questions. Thank you.

Sorry for the late response. Here are the answers to questions in comment #8:
1. To build Release version of ChromeDriver on Windows, make sure you have the following lines in your args.gn:
    is_debug = false
    target_cpu = "x86"
    is_component_build = false
and then run the following command (note the uppercase -C):
    ninja -C out/Release chromedriver

2. kCallFunctionScript has the following contents, where <call_function.js> is the contents of that file.
    function() { <call_function.js>;
                         return callFunction.apply(null, arguments) }
This string constant is generated by chrome/test/chromedriver/embed_js_in_cpp.py, which is automatically called during the build.

3. To build ChromeDriver that is close to the official released version, the best thing to do is to run the official version on the command line, and note the git hash that is displayed on the screen. Then you can use git to check out the commit using that hash.

Re comment #5, the cache key was randomly chosen by us (the prefix "cdc" stands for "ChromeDriver cache"). A web site that uses the same key is likely to be intentional rather than accidental.