feat(api): introduce locator.waitFor

[pavelfeldman]

Fixes #8577

[Phonesis]

Is this now live? I don't see a waitFor() option on my locators with 1.15.2

[yury-s]

I will be released in 1.16 as 1.15 api is already published.

[Phonesis]

@yury-s Thanks for update. Out of interest, will this waitFor() function support options for timeout and state? I am hoping to do something like this and call it via a page object:

  async isElementVisible(elementLocator: Locator, waitTime: number = 3000): Promise<boolean> {
    try {
      await elementLocator.waitFor({ 
        state: 'visible',
        timeout: waitTime,
      });
    }
    catch {
      return false;
    }
    return true;
  }

[yury-s]

Out of interest, will this waitFor() function support options for timeout and state?

Yes, it will support both.

It's already available in @next version of playwright, you can give it a try with npm i playwright@next.

[sarweshkumar2018]

How to handle if the locator returns more than one elements.
await this.page.locator('[aria-label="bene"]').waitFor();

await this.page.locator('[aria-label="bene"]:first-child').waitFor() --- is NOT working

[xyide]

How to handle if the locator returns more than one elements.

I don't think it would be necessary to handle this case. If any element with a given selector us visible, then naturally the first-child is visible.