- Issue created by @rkoller
- π¨π¦Canada mgifford Ottawa, Ontario
Yellow is just such a difficult color for contrast. Orange is easier.
- π¨π¦Canada mgifford Ottawa, Ontario
The current color can be described by:
hsl(46, 67%, 52%)
rgb(216, 178, 52)
#D8B234I'm no color expert but changing it to this
hsl(41, 95%, 31%)
rgb(157, 110, 4)
#9D6E04Would meet color contrast accordign to Tanaguru.com's Contrast Finder.
- π©πͺGermany jurgenhaas Gottmadingen
Tests are failing because the change was made in the
dist/css
directory, which contains files that get generated by a preprocessor. Changes need to be made in thestyles
directory and thennpm build
needs to be called which updates the distribution files.Also, color codes are using lower case characters.
- π¨π¦Canada mgifford Ottawa, Ontario
Ok.. I don't know what to do from here though https://git.drupalcode.org/project/gin/-/merge_requests/635/diffs
- π©πͺGermany jurgenhaas Gottmadingen
What's required is to run
npm build
locally in your dev environment. That will compile the changes into the distribution files and the result should then also be committed to the MR. - π¨π¦Canada mgifford Ottawa, Ontario
Sadly, I need more information. This is a 3 line change (one little search/replace). npm build locally doesn't work for me
Unknown command: "build"
.It is a pretty trivial patch, but I still don't know how to contribute it.
diff --git a/styles/theme/variables.scss b/styles/theme/variables.scss index 8e37e68b..ede2f940 100644 --- a/styles/theme/variables.scss +++ b/styles/theme/variables.scss @@ -12,7 +12,7 @@ --gin-color-disabled-bg: #eaeaea; --gin-color-disabled-border: #c2c2c2; - --gin-color-warning: #d8b234; + --gin-color-warning: #9d6e04; --gin-color-warning-light: #efcf64; --gin-bg-warning: #{mix(black, #efcf64, 70%)}; --gin-bg-warning-light: rgba(226, 151, 0, .08); @@ -35,7 +35,7 @@ --gin-status-bg: #eee; --gin-status-success-text: #1d6844; --gin-status-success-bg: #26a76930; - --gin-status-warning-text: #{mix(black, #d8b234, 40%)}; + --gin-status-warning-text: #{mix(black, #9d6e04, 40%)}; --gin-status-warning-bg: rgba(226, 151, 0, .15); --gin-status-danger-text: #cc3d3d; --gin-status-danger-bg: rgba(222, 117, 96, .15); @@ -292,7 +292,7 @@ --gin-status-bg: rgba(255, 255, 255, 0.12); --gin-status-success-text: #8bd3b1; --gin-status-success-bg: #26a76940; - --gin-status-warning-text: #{mix(white, #d8b234, 40%)}; + --gin-status-warning-text: #{mix(white, #9d6e04, 40%)}; --gin-status-warning-bg: rgba(226, 151, 0, .15); --gin-status-danger-text: #{mix(white, #cc3d3d, 50%)}; --gin-status-danger-bg: rgba(222, 117, 96, .15);
- First commit to issue fork.
- π©πͺGermany jurgenhaas Gottmadingen
This is looking good now, setting to "Needs review" so that people can test and review this.
@mgifford just FYI, the
npm build
command needs to be run in the Gin directory. But @siddharthjain has now done it for us, thank you. - π¨π¦Canada mgifford Ottawa, Ontario
Thanks @siddharthjain_7998 & @jurgenhaas
I'll try to figure this out in the future.