[Feature] innerText not defined in evaluate context

[thernstig]

    const foo= await page.waitForSelector('text="Something"');
    expect(await foo.evaluate(el => el.innerText)).toBe('Something');

Here innerText is not a type (if you e.g. use VS Code for autocompletion) whereas textContent is. It would be nice to add innerText into the TypeScript definitions.

(On a side-note it is quite verbose to get some text then assert on it, as above, but I don't think there is a nicer way (one-liner) for this?)

[aslushnikov]

Here innerText is not a type (if you e.g. use VS Code for autocompletion) whereas textContent is. It would be nice to add innerText into the TypeScript definitions.

cc @JoelEinbinder - can we actually do this?

On a side-note it is quite verbose to get some text then assert on it, as above, but I don't think there is a nicer way (one-liner) for this?

@thernstig yeah, no one-liner here. You can use page.waitFor to cut a little on the number of characters you use

[JoelEinbinder]

#1166 fixes a lot of case like this, but I believe this actually working as intended. innerText does not exist on SVGElements, so you can't rely on it here unfortunately. If you know you are getting an HTMLElement, you can cast it with typescript or in js with JSDoc:

/** @type {playwright.ElementHandle<HTMLElement>} */
const foo = await page.waitForSelector('text="Something"');

[thernstig]

@JoelEinbinder @alukyan This might be of interest. The above case was in regards to waitForSelector. Changing it to waitFor (with a string like above as input), it gives no autocompleteion at all for the el.. Is that "fixable"?