[Feature] | Add a new `enable|disable` state to waitForSelector.

I would like to have a page.waitForSelector state to check for enable|disable so that I can use the auto waiting feature when executing validations.

My use case:

• I get to a page where buttonA is disabled.
• After I fill some fields, my website does a request and based on the response it enables buttonA.
• Then I can change the fields, execute the requests again, and make sure that buttonA should be disabled again.

Note: I don’t want to click the button just validate it’s state.

Example:

expect(await page.waitForSelector('buttonA', { state: 'visible' })).toBeTruthy();
await page.click('buttonB');
expect(await page.waitForSelector('buttonA', { state: 'enabled' })).toBeTruthy();
await page.click('buttonC');
expect(await page.waitForSelector('buttonA', { state: 'disabled' })).toBeTruthy();

[pavelfeldman]

await expect(locator).toBeEnabled();

is a new way to asserting this.

[pjcalvo]

await page.waitForFunction(() => {
   return document.querySelector('foo').enabled;
});

Then what is the point of page.waitForLocator({state: visible}) … That can also be checked using {trial: true} on click…

IMO I think that extending the waitForLocator would be a great for user experience…