You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
slide toggle does not match app theme definition when base is set (to a value other than the default 500 'level')
What is the expected behavior?
That Slide-toggle @input() color: ThemePalette matches app theme definition when base is defined so that slide-toggle will match other themed components
What is the current behavior?
Slide toggle is fixed at the 500 level for each theme color: e.g., primary, accent and warn.
What are the steps to reproduce?
) set app theme to values other than default; e.g.,
The text was updated successfully, but these errors were encountered:
MichaelScottBurke
changed the title
Slide Toggle theme color does not follow app theme definition, but is fixed at 500 level default
Slide-toggle theme color does not follow app theme definition, but is fixed at 500 level default
Sep 8, 2018
Bug:
slide toggle does not match app theme definition when base is set (to a value other than the default 500 'level')
What is the expected behavior?
That Slide-toggle @input() color: ThemePalette matches app theme definition when base is defined so that slide-toggle will match other themed components
What is the current behavior?
Slide toggle is fixed at the 500 level for each theme color: e.g., primary, accent and warn.
What are the steps to reproduce?
button: #0d47a1 = 700 (accent, base from mat-blue-palette)
chip: #0d47a1 = 700
slide toggle: #2196f3 = 500
What is the use-case or motivation for changing an existing behavior?
The switch does not match my other themed components, it is lighter
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
Angular 6+, Angular Material 6+, mac os, all browsers
Is there anything else we should know?
issues seems to be in setting the thumb-checked-hue to 'default' in light theme in the slide-toggle theme
The text was updated successfully, but these errors were encountered: