wrapTimer changes browser's setTimeout behaviour

[karel1980]

Current behavior:

I have an application which calls setTimeout(undefined, 0). (This itself is not very good, but just for now, consider that this does nothing in Chrome (no errors).

Link to the setTimeout(undefined, 0) call: mdbootstrap/mdb-angular-ui-kit#97

Before cypress 3.1.1 this did not cause any errors. Since 3.1.1 this causes tests to fail in wrapTimer -> invoke (it tries to call 'apply' on the undefined argument).

Desired behavior:

Silently do nothing, just as a user's browser would do.

Steps to reproduce:

Build an application which calls setTimeout(undefined, 0) & run a test with cypress 3.1.1.

Versions

Cypress 3.1.1, reproduced on recent osx and ubuntu versions.
ps cypress 3.1.1 is available on npmjs.com, but not tagged on github? Is that intentional?

[chrisbreiding]

Yeah, I think we only handle a string or a function being passed in. We need to handle other types of values as well.

[brian-mann]

Released in 3.1.2.