Skip to content

Conversation

crisbeto
Copy link
Member

Fixes that the datepicker had some <label> elements that weren't pointing to anything via the for attribute which was being flagged by Chrome.

Fixes #29749.

Fixes that the datepicker had some `<label>` elements that weren't pointing to anything via the `for` attribute which was being flagged by Chrome.

Fixes angular#29749.
@crisbeto crisbeto added the target: patch This PR is targeted for the next patch release label Sep 18, 2024
@crisbeto crisbeto requested a review from a team as a code owner September 18, 2024 08:57
@crisbeto crisbeto requested review from amysorto and mmalerba and removed request for a team September 18, 2024 08:57
@crisbeto crisbeto added the action: merge The PR is ready for merge by the caretaker label Sep 18, 2024
@crisbeto crisbeto merged commit 602bef1 into angular:main Sep 18, 2024
22 of 25 checks passed
crisbeto added a commit that referenced this pull request Sep 18, 2024
…9755)

Fixes that the datepicker had some `<label>` elements that weren't pointing to anything via the `for` attribute which was being flagged by Chrome.

Fixes #29749.

(cherry picked from commit 602bef1)
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Oct 19, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

bug(material/datepicker): Chrome; A <label> isn't associated with a form field
2 participants