Skip to content

bug: goto() and waitForChanges() can return before all components hydrate #57

@nwhittaker

Description

@nwhittaker

Prerequisites

Stencil Playwright Version

0.2.1

Current Behavior

Given enough network latency and a 3rd-party Stencil component nested inside a local component, the Page.goto() and/or Page.waitForChanges() methods can return before the 3rd-party Stencil component finishes hydrating.

Expected Behavior

Nested, 3rd-party components are included in the goto() and waitForChanges() waiting.

Steps to Reproduce

  1. Checkout the repo and switch to the @stencil/playwright/waitForChanges-nested-sb branch, if needed.
  2. Run npm install
  3. Run npm run build
  4. Run npx playwright install, if needed
  5. Run npm run test
  6. See the "label with nested component over default network" passes while the "label with nested component over slow network" fails

Code Reproduction URL

http://github.com/nwhittaker/stencil-component/tree/%40stencil/playwright/waitForChanges-nested-sb

Additional Information

No response

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