Skip to content

bug(mat-checkbox): does not follow material design guide #30771

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

Open
1 task
smil-thakur opened this issue Apr 2, 2025 · 0 comments
Open
1 task

bug(mat-checkbox): does not follow material design guide #30771

smil-thakur opened this issue Apr 2, 2025 · 0 comments
Labels
needs triage This issue needs to be triaged by the team

Comments

@smil-thakur
Copy link

smil-thakur commented Apr 2, 2025

Is this a regression?

  • Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was

No response

Description

Image

in the above image you can see the checkbox get intended to right because it aligns itself from touch-target 48x48 to make it align with the text we have to apply negative margin to it which is not a good practice

Image

On the official website of m3 design (https://m3.material.io/components/checkbox/accessibility) the checkbox inner box is aligned with the title,

so can you clear out the confusion that which is correct, if our material alignment is correct can we have reason for it and if m3 doc is correct can we look into this bug

Reproduction

https://material.angular.io/components/checkbox/overview

Expected Behavior

it should be aligned with the title or with the flow of the page, the box inside should be align with edge of the page

Actual Behavior

checkbox get intended to right because it aligns itself from touch-target 48x48

Environment

  • Angular: 19
  • CDK/Material: 19
  • Browser: chrome
  • Operating System: windows
@smil-thakur smil-thakur added the needs triage This issue needs to be triaged by the team label Apr 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs triage This issue needs to be triaged by the team
Projects
None yet
Development

No branches or pull requests

1 participant