find('.foobar').click(x: 120, y: 10). When running on Selenium 4.2.1, this code works fine. I do see a warning however -
WARN Selenium moving to an element with offset currently tries to use the top left corner of the element as the origin; in Selenium 4.3 it will use the in-view center point of the element as the origin.- which comes exactly from that line. I guess that is related to the problem?
have_no_textisn't defined to work with an array, and I would be shocked if it did. It'll call
to_son the array and then verify that your page doesn't have whatever that string equivalent of the array is. I also wonder why you'd think what
have_no_textaccepts would have any relevance on what
have_no_textin the wrong way for a while! :D Thankfully just in one place.
have_none_of_selectorsdoesn't seem to fit exactly what I need I believe - I want to check that something doesn't contain any of the strings that I pass - for example
expect(page).to have_no_text(['foo', 'bar', 'baz'])- i.e. I want the current scope to not contain either of the three strings. I'm not sure that's possible with
have_none_of_selectors? Perhaps that could be a feature request. :)
disabled?does not take it into account .
capybara-screenshotafter I've done
page.driver.browser.action.move_to(link).click_and_hold.move_to(link, 100, 100).perform(which means the page is in a "dragging" state) but the mouse (and hence what is dragged) is not captured in the screenshot. Any ideas?