Conversation
Adding it in twice is bad -- the first time shouldn't need it? May need to evaluate dependencies for what Core ships and bundles though for less/sass.
This uses specificity to match Core styles and adjusts the height to accomodate core style changes.
We need to maintain an old version of the file for pre-4.9 versions of WordPress as we support vCurr and vCurr - 1.
This should help clear out the cruft. Let's start over and rearchitect the file.
We need this to be `jetpackCss`
We don't really need to override it any longer, I don't think.
|
This PR is dependent on https://core.trac.wordpress.org/changeset/41974 being in your core checkout. If something's screwy, try a |
|
Please test this for functionality and behavior, as well as regressions. |
Otherwise the gutter may not get the errors displayed in it.
Simpler to read code yields better maintainability.
|
If testing this, make sure you're up to https://core.trac.wordpress.org/changeset/41992 on your core checkout. |
|
Tested with Core both before 41992 and after, everything seems to be working correctly. There's one minor problem that I have noticed. If you follow these steps:
|
|
To clarify, the errors only display when the mode is set to CSS right? That's expected as it's invalid css. |
|
Or do you mean that the css persists but preprocessor selection doesn't? @zinigor |
|
Yes, sorry, I meant that the selector persists, but the errors still get displayed as though it's set to be simple CSS. |
|
Got the design review from @MichaelArestad yesterday, clearing the tag. |
zinigor
left a comment
There was a problem hiding this comment.
Disregard my latest comment - I can no longer reproduce the problem, plus it was really minor, should not be a problem to anyone.


Fixes #7794
Minimum revision of core to test against: https://core.trac.wordpress.org/changeset/41992