bug(Toolbar): Defined background colors does not get applied with version 17.3.1
- Dominant language
- TypeScript
- Stars
- 25k
- Forks
- 6.8k
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 91
Description
### Is this a regression?
- [X] Yes, this behavior used to work in the previous version
### The previous version in which this bug was not present was
16
### Description
If you go to the official `Angular Material` docs, and select component `Toolbar`, examples tab, you see in action the usage of toolbar with a color defined such as `primary` but you don't see any color applied to it.
If you open up any of the examples to Stackblitz, you can clearly see that any of the defined colors "warn", "primary", "accent" does not get applied in the toolbar property
```
...
...
...
```

### Reproduction
StackBlitz link: https://stackblitz.com/edit/ga5498?file=src%2Fexample%2Ftoolbar-overview-example.html
Steps to reproduce:
1. Specify one of the colors predefined such as `warn`, `primary`, `accent` to the toolbar component
### Expected Behavior
If the developer specifies a color to a toolbar, either a predefined one or a custom one, then the color should take effect into the material component (e.g toolbar)
### Actual Behavior
Specifying any of the predefined colors does not get applied in the toolbar component
### Environment
- Angular: 17.3.0
- CDK/Material: 17.3.1
- Browser(s): Firefox 124.01 or Chrome 123.0.6312.86
- Operating System (e.g. Windows, macOS, Ubuntu): Linux Mint
Contributor guide
Research direction
Start with the linked StackBlitz reproduction and its src/example/toolbar-overview-example.html file, then compare the toolbar behavior across the reported Angular Material versions. Verify the primary, accent, warn, and custom colors and identify the relevant project entry point or test before changing anything. Done means the toolbar applies the specified colors and the regression is covered by a passing check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angular
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100