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
the getRowElementsWhere() looks to be returning the correct number of rows and columns for the matcher included with the call, however the locator for each row is not unique:
.//tr[td][count(td)>=9]
matchingElements.add(rowElements.get(index))
It really doesn't matter which index is used in the above statement, as each row locator is returned with the same value.
Perhaps returning something like:
.//tr[td][count(td)>=9][3] .
with 3 being the matching row(s) index
This means that any action I perform on the matched rows will only hit the first row of the table as the above locator is finding all the rows and not the actual matched row. Not a problem if the match happens to be the first row, but if not I dont get what I want.
taking a look at the HtmlTable class it looks like the index for the matched row is never attached to the generated locator.
version 1.6.3
The text was updated successfully, but these errors were encountered:
@tfrothingham I have the same issue when the table is horizontally scrollable. The .size() method returns the proper count but the getHeaders() method is only returning what is visible without scrolling.
In my case fourteen of the fifteen columns are visible and the scrollbar is active, as a result, only fourteen headers are returned. I proved my case by inserting within the test a pause long enough to allow me to maximize the browser window.
I have yet to determine how to achieve a resolution programmatically.
the getRowElementsWhere() looks to be returning the correct number of rows and columns for the matcher included with the call, however the locator for each row is not unique:
.//tr[td][count(td)>=9]
matchingElements.add(rowElements.get(index))
It really doesn't matter which index is used in the above statement, as each row locator is returned with the same value.
Perhaps returning something like:
.//tr[td][count(td)>=9][3] .
with 3 being the matching row(s) index
This means that any action I perform on the matched rows will only hit the first row of the table as the above locator is finding all the rows and not the actual matched row. Not a problem if the match happens to be the first row, but if not I dont get what I want.
taking a look at the HtmlTable class it looks like the index for the matched row is never attached to the generated locator.
version 1.6.3
The text was updated successfully, but these errors were encountered: