Thanks to visit codestin.com
Credit goes to github.com

Skip to content

bug(form-field): difficult to customize shape with tokens #31059

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
svg94 opened this issue May 9, 2025 · 0 comments
Open
1 task

bug(form-field): difficult to customize shape with tokens #31059

svg94 opened this issue May 9, 2025 · 0 comments
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent

Comments

@svg94
Copy link

svg94 commented May 9, 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

19

Description

When using mat-form-field in filled appearance, I want to shape the border-radius. I use this token
--mdc-filled-text-field-container-shape: 4px !important;
But it only applies to the top corners and not the bottom corners because this token uses the wrong container to set radius. It sets the radius on a level where the div for hints and errors is also included.
And by that the bottom corners are not set with that token

Reproduction

StackBlitz link:
Steps to reproduce:
1.
2.

Expected Behavior

Apply radius also to bottom corners

Actual Behavior

not applying radius to bottom corners

Environment

  • Angular: 19
  • CDK/Material: 19
  • Browser(s): firefox
  • Operating System (e.g. Windows, macOS, Ubuntu): windows
@svg94 svg94 added the needs triage This issue needs to be triaged by the team label May 9, 2025
@andrewseguin andrewseguin changed the title bug(COMPONENT): TITLE bug(form-field): difficult to customize shape with tokens May 14, 2025
@andrewseguin andrewseguin added P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent and removed needs triage This issue needs to be triaged by the team labels May 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P3 An issue that is relevant to core functions, but does not impede progress. Important, but not urgent
Projects
None yet
Development

No branches or pull requests

2 participants