Skip to content

Handling platforms with limits on background execution #1034

@gsnedders

Description

@gsnedders

Both Android and iOS have varying restrictions on background execution.

As such, it is often undesirable for a browser under automation control to be moved to the background.

However, with platform features such as Android App Links and iOS's universal links, even something as seemingly benign as an HTTP/HTTPS URL can in fact bring another app to the foreground — which on devices which allow only a single app to be in the foreground at a time implicitly moves the browser to the background.

Maybe the answer is we shouldn't at a spec level worry about such issues — and just let the WebDriver session be in an unusable state once the browser has been moved to the background — but it does seem worthwhile considering what we want to do in such cases.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions