Skip to content

slowMo options is supported when connecting to a Chromium instance #180

@yujiosaka

Description

@yujiosaka

What is the current behavior?

Currently slowMo option is supported only when launching a Chromium instance, and not when connecting an existing Chromium instance

What is the expected behavior?

It should be supported when connecting an existing Chromium instance.

What is the motivation / use case for changing the behavior?

It was fixed upstream here.

Please tell us about your environment:

  • Version:
  • Platform / OS version:
  • Node.js version:

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions