Closed martinpelikan closed 7 years ago
Hi martinpelikan!
Thanks for your PR. It looks good to me. This behavior is kind of tricky but the changes do not make the state of things worse. However before we merge this PR please could you:
One for SamplePage.anchor_list field (https://github.com/martinpelikan/webium/blob/f9a8a654f4dc147f00f79ebdeb8f9fc212f99f9b/tests/simple_page/__init__.py#L54) Other - for SamplePage.empty_element_list field (https://github.com/martinpelikan/webium/blob/f9a8a654f4dc147f00f79ebdeb8f9fc212f99f9b/tests/simple_page/__init__.py#L56)
@SUNx2YCH , @Khrol could please take a look as well?
I was able to spend some time today on addressing your reviews. Many thanks for being so quick to respond and review @Khrol and @ufranske!
Should my commit also include a version bump, or is this a responsibility of the maintainers?
Context I'm still quite new to the page object design pattern, so this may not normally come up. I have a table of elements that need to be deleted one at a time via a menu/option. My solution is to iterate while there are still elements visible and delete them one at a time (avoiding the stale element reference in doing so). The problem is that Webium's nice
is_element_present()
method fails for Finds. This is my fix, which seems to work for me, and should not break existing behaviour. The question is, if it should check that all elements are visible, or if only the first is necessary...Error Encountered