[Feature]: Order-Insensitive Collection Assertions

[gamestheory]

🚀 Feature Request

The hasText(String[] expected) assertion is strictly order-dependent. However, many UI components (like tags, filter chips, or list items) might appear in a non-deterministic order or the order might be irrelevant to the test case.

Example

Add a param to HasTextOptions or a new method to ignore order: hasText(String[] expected, boolean ignoreOrder) or hasTextInAnyOrder(String[] expected).

Motivation

Resilience to Change: Tests won't fail due to minor UI sorting changes that do not affect business logic.
Cleaner Test Code: Developers won't need to manually fetch, sort, and compare lists, which often bypasses Playwright's automatic retries.
Implementation: This can be implemented by internally sorting both the actual and expected collections before comparison when the flag is set.

[arnabnandy7]

Thanks for reporting this. Order-insensitive matching needs to be implemented in the shared Playwright assertion engine so that it preserves web-first retries, text normalization, regular-expression matching, and consistent behavior across language bindings.

The upstream implementation is being tracked in microsoft/playwright#41803, with the proposed fix in microsoft/playwright#41804.
Once that change is merged and included in a Playwright driver release, we can roll the driver into Playwright Java, expose HasTextOptions.setIgnoreOrder(true) through the generated Java API, and add Java integration coverage here. I’ll keep this issue open until the Java binding includes the feature.