Oops, sorry for the disruption. Yes, having "nopersistent" suppressing this behaviour makes sense to me.
Is there any way we could have found out about this breaking your use case earlier? casper has tests now, so if you can describe other use cases sufficiently precisely we can make sure we keep them working...
Oops, sorry for the disruption. Yes, having "nopersistent" suppressing this behaviour makes sense to me.
Is there any way we could have found out about this breaking your use case earlier? casper has tests now, so if you can describe other use cases sufficiently precisely we can make sure we keep them working...