No browser actions possible in callbacks

[lxanders]

Yesterday I tried to do something like this (I simplified the example a little bit):

browser
    .waitForElementPresent('section div output', 5000)
    .getValue('section div output', function (result) {
        if (result.value !== 'someInterestingValue') {
            browser
                .click('a.linkToAnotherPage')
                .waitForElementVisible('td.withSomeInterestingClass a', 5000)
                .click('td.withSomeInterestingClass a');
        }
    });
    .doTheRestOfTheTest...

The reason for this was, that the part in the callback should only trigger when the condition passes (here read by using getValue and the value of its result).

It seems that this is not working because the click method didn't find the element. Here is an excerpt of the console output:

...
ERROR: Unable to locate element: "td.withSomeInterestingClass a" using: css selector
✔  Element <td.withSomeInterestingClass a> was visible after 3245 milliseconds.
Unable to locate element: "td.withSomeInterestingClass a" using: css selector
FAILED:  1 errors and 2 passed
...

So it seems, that the first click is done and successful (I confirmed that by watching the test run) and then some things happen in the wrong order. As the second click should be done after the waitForElementVisible and this part was successful, the click should work too. It seems the error message is caused by not finding the same element it was waiting for because it is called too early.

My ideas were:

• First I thought the reason might be a problem with CSS selectors - reading the error message some times I don't think so anymore
• Second thought: The context might be different in the callback - so I tried saving the browser-variable to another variable and calling this in the callback - didn't work - same error as above
• There is a problem with the promises / asynchronity

[beatfactor]

It's a bug alright, a problem with the queuing mechanism.

[erickbrower]

A coworker of mine ran into this very bug yesterday! He was trying to do browser nav in the getAttribute() callback

[kineticac]

@beatfactor Got this error as well. The order of items executing is no longer guaranteed after a callback is executed. I've tried nesting assertions within the callback as well, but those are also out of order. Seems like you have a handle on it?

[beatfactor]

should be fixed.

[kineticac]

Works for me! Thanks for the quick fix!

[lxanders]

Works for me, too. Thanks!