fix(material/testing): Fix minor issue preventing the label
filter from working for some implementations
#31596
+46
−30
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates the FormFieldControlHarness label capabilities to support a wider range of implementations. This affects any harness that derives from MatFormFieldControlHarnessBase, such as MatInputHarness and MatSelectHarness.
The current implementation works as expected when searching for a floating mat-label within a mat-form-field. However, it fails when searching for a label that is provided via
<label for=...>
oraria-label
, as are suggested in the Material documentation. This change aims to expand support for these patterns to match the supporting documentation.