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
Describe the bug
This is related to the preview/dev build, using alabaster as default. These are the colors returned from Soho.theme.personalizationColors() in Light mode, which we use to build the color selector (dropdown is-swatch)
{
"default": {
"id": "default",
"name": "Default",
"backgroundColorClass": "primary-bg-color", <--- This seems to have wrong value
"value": "#0066D4" <--- Should this be white?
},
"alabaster": {
"id": "alabaster",
"name": "Alabaster",
"backgroundColorClass": "alabaster",
"value": "#ffffff"
},
// ... rest of accent colors
}
primary-bg-color in effect on the option
To Reproduce
I couldn't find the dev build deployed, but should be reproducible in an example that uses the swatch dropdown.
Expected behavior primary-bg-color should be white. And will alabaster still be kept as a personalization color? We could filter it out if we want to avoid duplicates (Default & Alabaster), with a fallback to default if alabaster has previously been selected, so more of a question.
Additional context
The default value itself works fine, i.e. headers/subheaders/tabs get alabaster. It's just the representation of it in the swatch.
Version
ids-enterprise: v4.89.0-dev.0
Platform
Infor Application/Team Name: OS Portal
The text was updated successfully, but these errors were encountered:
volante007
changed the title
Preview - Accent colors - Default shows incorrect in color selector, and should alabaster be kept as an option?
Preview - Accent colors - Default shows azure in color selector, and should alabaster be kept as an option?
Nov 7, 2023
Describe the bug
This is related to the preview/dev build, using alabaster as default. These are the colors returned from
Soho.theme.personalizationColors()
in Light mode, which we use to build the color selector (dropdown is-swatch)primary-bg-color
in effect on the optionTo Reproduce
I couldn't find the dev build deployed, but should be reproducible in an example that uses the swatch dropdown.
Expected behavior
primary-bg-color
should be white. And will alabaster still be kept as a personalization color? We could filter it out if we want to avoid duplicates (Default & Alabaster), with a fallback to default if alabaster has previously been selected, so more of a question.Additional context
The default value itself works fine, i.e. headers/subheaders/tabs get alabaster. It's just the representation of it in the swatch.
Version
Platform
The text was updated successfully, but these errors were encountered: