Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

bug(DIALOG): dialog's container-color does not follow Material 3 design specs

Open Beginner friendly
#30,536 0 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
64/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
angular, typescript
Domain
design, frontend

Research direction

No file or test is named. Locate the Angular Material dialog theming implementation and its existing tests, then compare the container-color token with the linked Material 3 dialog specification. Done means the default token uses surface-container-high and the relevant test coverage passes.

Written by the indexing model from the issue text.

Description

area: material/dialog P2
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

As per Material 3 guidelines, container-color should use value surface-container-high token, but it's using value surface token.

We can override it by using dialog-overrides mixin like below:

@include mat.dialog-overrides((
  container-color: var(--mat-sys-surface-container-high),
));

But, it should be the default behaviour as per Material 3 specs.

Reproduction

Not needed

Expected Behavior

As per Material 3 guidelines, container-color should use value surface-container-high token.

Actual Behavior

Dialog's container-color is using value surface token.

Environment
  • Angular: 19
  • CDK/Material: 19
  • Browser(s): Chrome
  • Operating System (e.g. Windows, macOS, Ubuntu): Windows
Dominant language
TypeScript
Stars
25k
Forks
6.8k
Avg merge
1d 2h
Merged PRs (30d)
80

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from angular/components

All issues in angular/components

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.