Opened 8 years ago
Closed 8 years ago
#38389 closed defect (bug) (fixed)
Twenty Seventeen: Refresh color patterns for changes in style.css
Reported by: | melchoyce | Owned by: | davidakennedy |
---|---|---|---|
Milestone: | 4.7 | Priority: | normal |
Severity: | normal | Version: | |
Component: | Bundled Theme | Keywords: | has-patch needs-testing |
Focuses: | Cc: |
Attachments (3)
Change History (19)
#2
@
8 years ago
- Summary changed from Twenty Seventeen: Colors: Header background, gallery images and captions, widget images, tables missing to Twenty Seventeen: Refresh color patterns for changes in style.css
Updating at least the ticket summary to reflect the approach here. I'm going to go through all of the changes made to style.css
after October 4th and sync them to both color-patterns.php
and colors-dark.css
. The colors files were forked from the stylesheet on that date, and organized by color.
@davidakennedy please ensure that every patch and commit to style.css
moving forward also makes the corresponding edits to the colors file. Any selector change with any colors in it, and definitely any changes to color-related properties (including border color) needs to be made in both places. I'll take care of everything that happened on GitHub, but the core merge is a good line for when color changes started being handled as changes are made.
#3
@
8 years ago
@celloexpressions Thank you and agreed! I'll keep an eye out for anything color related.
@
8 years ago
Update color-patterns.php for all commits to style.css between October 4th and core merge.
#4
@
8 years ago
- Owner changed from celloexpressions to davidakennedy
- Status changed from assigned to reviewing
38389.diff re-syncs the color-patterns.php
template with all of the changes between October 4th and core merge that were committed to style.css
. Unfortunately, the way git works, it's extremely tedious to do this since there are cross-merges across branches and a lot of iterations to diffs to fix coding standards, etc. in the history. This is pretty close, but I imagine there will be a few more bugs that spring up.
The dark scheme should probably be entirely remade based on the revised color patterns file. If someone can list out how each color should be mapped from the originals again that would help, then there are some additional color inversions that may be needed on top of it. I didn't apply custom colors to the dark playlist styles, and I suppose that if someone is using the dark scheme they'd select the dark playlist style anyway, so probably don't need to change anything there.
#7
@
8 years ago
Thanks @celloexpressions! This looks pretty good. The biggest issue I see is that the color schemes do not have the new link styles.
Those were brought in here: https://github.com/WordPress/twentyseventeen/pull/428
#8
@
8 years ago
They should have the new link styles, but there may be some bugs there. You can see that a big chunk of the diff moves link selectors from the background color to the black text color and the hover state override is also there. But it was hard for me to figure out exactly what might be missing, so if someone that worked on that change could make adjustments to 38389.diff as needed that would be great.
#9
@
8 years ago
Thanks @celloexpressions! @laurelfulford is going to take a stab at reviewing and updating anything.
#10
@
8 years ago
In 38389.1.diff I updated the styles to include the new link styles, in both the colors-dark.css and color-patterns.php. Hopefully that got everything - just let me know if anything isn't displaying as expected!
#12
@
8 years ago
It's hard to tell in the diff, but let's make sure that all of the color patterns remain ordered from light to dark or vice-versa in both of these files. And maybe double-check that there's a comment at the top indicating that, I think there may be one there already.
I unfortunately have to work on a couple of higher priority things so don't have time to test at the moment, but we can continue iterating and it's probably better to get the bulk of the fixes in sooner rather than later. We'll catch most of the lingering issues in beta.
#14
@
8 years ago
@laurelfulford This looks good. Almost ready for commit. One issue I see:
.project-terms
is referenced in the style.css
and is likely left over from Lodestar fork. Can you all traces? It's not needed.
#15
@
8 years ago
Updated the changes in 38389.2.diff - includes fixing one out-of-order colour, adding a comment to each file about the colours being in order, and removing the unneeded .project-terms
selector from the style.css and both colour files.
Just let me know if there's anything else!
Assigning to celloexpressions as said on GitHub would tackle this.