New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(material-experimental/mdc-list): make internal input non-interactive #21438
Conversation
We should probably not bother with this change since MDC is rewriting their list from scratch (to be more like our's with different variants) |
Due to how MDC's checkbox styles are set up, we always have to keep an `input` inside the `mat-list-option`, however our current setup where we only set `tabindex="-1"` on it is invalid, because the input is still interactive either through clicking on it, or by using a screen reader's forms mode. These changes completely remove the input from the accessibility model by setting it to `display: none`.
4880a5e
to
9d2b8c6
Compare
@jelbourn I'm not familiar with what their new list will look like, but I think that we'll have to keep doing this if we're projecting in a checkbox |
That's fair |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
…ive (#21438) Due to how MDC's checkbox styles are set up, we always have to keep an `input` inside the `mat-list-option`, however our current setup where we only set `tabindex="-1"` on it is invalid, because the input is still interactive either through clicking on it, or by using a screen reader's forms mode. These changes completely remove the input from the accessibility model by setting it to `display: none`. (cherry picked from commit c268246)
…ive (angular#21438) Due to how MDC's checkbox styles are set up, we always have to keep an `input` inside the `mat-list-option`, however our current setup where we only set `tabindex="-1"` on it is invalid, because the input is still interactive either through clicking on it, or by using a screen reader's forms mode. These changes completely remove the input from the accessibility model by setting it to `display: none`.
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Due to how MDC's checkbox styles are set up, we always have to keep an
input
inside themat-list-option
, however our current setup where we only settabindex="-1"
on it is invalid, because the input is still interactive either through clicking on it, or by using a screen reader's forms mode.These changes completely remove the input from the accessibility model by setting it to
display: none
.