So while tooling around on some stuff, I was trying different ways to use
selectors in conjunction with some array values. I came across something
that I can't quite figure out.
I recreated it using http://automationpractice.com/index.php to be able to
ask in general without need for people
8.1 Pro
On Wednesday, June 20, 2018 at 9:14:25 PM UTC-4, Steve Parrado wrote:
>
> I recreated it by navigating to a public facing website, identifying an
> element at the top of the page, and then scrolling down and performing the
> click and click+control. Here is the output:
>
af/keys |
{"value":["î?%"]}
2018-06-20 21:09:01 INFO Selenium <-
{"sessionId":"347b09a05ad4e6ffe8661cb3a0b0a9af","status":0,"value":null}
=> nil
What I noticed here is that the ".click(:control)" actually clicked the
Has anyone seen similar behavior? I am still at a loss about this.
On Thursday, June 7, 2018 at 12:00:07 AM UTC-4, Steve Parrado wrote:
>
> I was attempting to write a function that performed a ctrl+click so that
> if the click caused a page navigation, it would be in a new win
I was attempting to write a function that performed a ctrl+click so that if
the click caused a page navigation, it would be in a new window which would
leave the original window in a particular state. It was during this that I
found that when I click an element that is obscured by another
