You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Watir, when you try to find an element by index, it should begin with 1, instead of 0 (this limitation comes from Internet Explorer DOM, where indexing begins with 1).
To maintain compatibility, this should be changed in watir-webdriver.
Please comment :)
The text was updated successfully, but these errors were encountered:
This might be a big limitation for users (like me) with couple of thousand line of existing Watir code. Btw, I did a local workaround in normalized_selector()
I wonder if we could introduce something during startup, like new(symb, index_offset = 0) to make it even more compatible with Watir?
In Watir, when you try to find an element by index, it should begin with 1, instead of 0 (this limitation comes from Internet Explorer DOM, where indexing begins with 1).
To maintain compatibility, this should be changed in watir-webdriver.
Please comment :)
The text was updated successfully, but these errors were encountered: