Why it's not a bug?
Take any html file, select_list part is acting in a same way, that is, it's
not waiting for select_list to exist, for an example, consider the code
below
require 'watir'
b.goto 'bit.ly/watir-webdriver-demo'
b.element(id: 'entry_10').send_keys 'Hi'
I made a mistake in
The object may not be visible
The first hack is to add a sleep before the select. Not elegant but the
kludge usually works
sleep 30
A better method is to wait for it to be present
b.select_list(:id => 'entry_1').when_present.select('Ruby')
or
b.select_list(:id => 'entry_1')..wait_until_
when_present is not necessary now because it's implicit since WATIR 6.0
ONWARDS.
On Aug 10, 2017 9:34 PM, "Super Kevy" wrote:
> The object may not be visible
> The first hack is to add a sleep before the select. Not elegant but the
> kludge usually works
> sleep 30
>
> A better method is to wai
So the option list is probably not populated yet. Maybe its a generated
list.
Then wait for the option to be present
browser.select_list(:id => 'theId').option(:value =>
'Ruby').wait_until_present
browser.select_list(:id => 'theId').option.wait_until_present
On Thursday, August 10, 2017 at 1
You were right, the update in 6.4 changed how options get waited for on
Select Lists.
Fix is here: https://github.com/watir/watir/pull/619
Will be in the 6.7 release whenever that happens
Thanks for providing a reproducible case.
On Thursday, August 10, 2017 at 2:14:50 AM UTC-5, Raja gopalan w