-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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(radio): Move .mat-radio-input above .mat-focus-indicator. #18709
Conversation
can apply styles to .mat-focus-indicator with CSS based upon whether or not .mat-radio-input is focused.
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
Marking as merge safe since Zack already ran a TGP for this PR |
* fix(radio): Move .mat-radio-input above .mat-focus-indicator so that we can apply styles to .mat-focus-indicator with CSS based upon whether or not .mat-radio-input is focused. * Explicitly add comment explaining why ripple must come after input.
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. |
The reason why we want to do this is so that we can apply styles to
.mat-focus-indicator
based upon whether or not.mat-radio-input
is focused. We can't do this right now, because we there is no way to "look backwards" with CSS selectors. After this change, we will be able to write:This change also aligns the DOM structure of radio button with checkbox and slide toggle (the two latter components already have their inputs before the focus indicator element in the DOM).
Ran TGP, no failures.