Update WebDriver atoms to pick up r17582.

Update WebDriver atoms to r17589 to pick up r17582.

This fixes the find elements command when used on pages with prototype JS lib.
BUG=chromedriver:102
TEST=none

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=148795

[dennis_jeffrey, 2012-07-27 00:19:30]

The README file says the atoms were generated from version 17589, but the CL
description says 17582.

https://chromiumcodereview.appspot.com/10829048/diff/1/chrome/test/webdriver/...
File chrome/test/webdriver/test/bad_native_funcs.html (right):

https://chromiumcodereview.appspot.com/10829048/diff/1/chrome/test/webdriver/...
chrome/test/webdriver/test/bad_native_funcs.html:35: }
nit: indent lines 3-35 by 2 spaces each

https://chromiumcodereview.appspot.com/10829048/diff/1/chrome/test/webdriver/...
chrome/test/webdriver/test/bad_native_funcs.html:39: Tests that no native
functions are called by ChromeDriver.
nit: indent this line by 2 spaces

https://chromiumcodereview.appspot.com/10829048/diff/1/chrome/test/webdriver/...
File chrome/test/webdriver/test/chromedriver_tests.py (right):

https://chromiumcodereview.appspot.com/10829048/diff/1/chrome/test/webdriver/...
chrome/test/webdriver/test/chromedriver_tests.py:1156:
driver.find_element_by_tag_name('body').find_elements_by_tag_name('div')
do we need to assert anything here?  Or is the test just verifying that we can
find the element without any errors being thrown?

[zori, 2012-07-27 00:41:34]

https://chromiumcodereview.appspot.com/10829048/diff/1/chrome/test/webdriver/...
File chrome/test/webdriver/test/chromedriver_tests.py (right):

https://chromiumcodereview.appspot.com/10829048/diff/1/chrome/test/webdriver/...
chrome/test/webdriver/test/chromedriver_tests.py:1156:
driver.find_element_by_tag_name('body').find_elements_by_tag_name('div')
So 'find_element_by_tag_name' would not have exposed the bug, right?

[kkania, 2012-07-27 15:48:31]

Its updated to 17589, although we only care about 17582. I updated the CL
description to make it more clear.

https://chromiumcodereview.appspot.com/10829048/diff/1/chrome/test/webdriver/...
File chrome/test/webdriver/test/bad_native_funcs.html (right):

https://chromiumcodereview.appspot.com/10829048/diff/1/chrome/test/webdriver/...
chrome/test/webdriver/test/bad_native_funcs.html:35: }
On 2012/07/27 00:19:30, dennis_jeffrey wrote:
> nit: indent lines 3-35 by 2 spaces each

Done.

https://chromiumcodereview.appspot.com/10829048/diff/1/chrome/test/webdriver/...
chrome/test/webdriver/test/bad_native_funcs.html:39: Tests that no native
functions are called by ChromeDriver.
On 2012/07/27 00:19:30, dennis_jeffrey wrote:
> nit: indent this line by 2 spaces

Done.

https://chromiumcodereview.appspot.com/10829048/diff/1/chrome/test/webdriver/...
File chrome/test/webdriver/test/chromedriver_tests.py (right):

https://chromiumcodereview.appspot.com/10829048/diff/1/chrome/test/webdriver/...
chrome/test/webdriver/test/chromedriver_tests.py:1156:
driver.find_element_by_tag_name('body').find_elements_by_tag_name('div')
On 2012/07/27 00:19:30, dennis_jeffrey wrote:
> do we need to assert anything here?  Or is the test just verifying that we can
> find the element without any errors being thrown?

Yes, any error should result in an exception. i added a comment.

https://chromiumcodereview.appspot.com/10829048/diff/1/chrome/test/webdriver/...
chrome/test/webdriver/test/chromedriver_tests.py:1156:
driver.find_element_by_tag_name('body').find_elements_by_tag_name('div')
On 2012/07/27 00:41:34, zori wrote:
> So 'find_element_by_tag_name' would not have exposed the bug, right?

right, just the plural version

[dennis_jeffrey, 2012-07-27 16:47:12]

LGTM

[commit-bot: I haz the power, 2012-07-27 17:50:19]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/kkania@chromium.org/10829048/7

[commit-bot: I haz the power, 2012-07-27 20:43:24]

Change committed as 148795