Skip to content

Redesign browser pool and the whole browsers subpackage #1744

@vdusek

Description

@vdusek

Note: This is a starting point for discussion, not a final decision. The team should review and adjust before any implementation begins.❗

Context

The browser pool and the whole browsers subpackage have several architectural issues and poor abstractions. These make it difficult to extend (e.g., remote browser support in #1743 and maybe even lifecycle hooks in #1741). We've discussed these issues a few times already. With the introduction of #1743, this may be a good opportunity to finally establish a well-structured and robust design for the browser pool. This effort should also be coordinated with the new user pool initiative in #1435.

Reference

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request.t-toolingIssues with this label are in the ownership of the tooling team.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions