So, the way it works, is that after a user has verified their email, a structure is set in localStorage called usersComputer. Initially, for a given user, the `state` is `seen` and it sets an `updated` timestamp. Signing-in again in less than 60 seconds from `updated` will mean that the dialog will challenge them with 'Is this your computer?'. Either answer (yes/no) means they will not be asked again at a later time.

Yeah, this is a pain in the ass for for deterministic testing on selenium/saucelabs where delays can happen.

One thing in looking at the full file is that there seem to a historical collection of locators and methods on dealing with this.

Aside from polling from completion, an alternative approach (not necessarily recommending it) is the alter localStorage with JS. Yeah, forget I said that ;-)