page.getByText doesn't support RTL options

[kettanaito]

Describe the bug

The page.getByText() locator, while being similar to RTL's .getByText(), doesn't support the normalizer and other options available in RTL.

I consider this a bug for two reasons:

1. This difference in behavior isn't listed in Vitest's docs.
2. The docs even reference RTL's docs, which I read as "Learn more about this API because it's quite the same".

I find options like normalizer quite lacking since I don't see how you would select an element which text content is broken by a non-text UI element (you'd use normalizer for that).

Reproduction

Unfortunately, this is a docs/implementation issue.

System Info

—

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[AriPerkkio]

These locators are from Playwright. Their API is inspired by @testing-library but not identical due to technical implementation. From Vitest's side I don't think there's anything we can do. https://playwright.dev/docs/api/class-framelocator#frame-locator-get-by-text