-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix stylelint errors in scss files #32386
Conversation
Here is how your PR affects size of JS and CSS bundles shipped to the user's browser: Webpack Runtime
Legacy SCSS Stylesheet
Sections
Async-loaded Components
Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory. Generated by performance advisor bot at iscalypsofastyet.com. |
8e82f3e
to
c7dfab7
Compare
c7dfab7
to
b9d06c8
Compare
Rebased and dropped the Prettier commit 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for a nice cleanup! 👍
|
@@ -322,7 +322,7 @@ | |||
} | |||
|
|||
.signup-processing-screen__loader, | |||
.signup-processing-screen__loader:after { | |||
.signup-processing-screen__loader::after { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This may change the behaviour as :after
might not always work. Did you test it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually you can ignore this:
Browsers also accept :after, introduced in CSS2.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@scruffian When does :after
and ::after
behave differently? MDN says that the single colon is a CSS2 thing, two colons got introduced in CSS3. My guess would be that the difference was an issue in 2005.
left: 0px; | ||
right: 0px; | ||
left: 0; | ||
right: 0; | ||
box-shadow: -3px 1px 10px -2px rgba( var( --color-neutral-700-rgb ), 0.075 ); | ||
|
||
@media only screen and ( min-width: 480px ) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sidenote: it would be good to lint for these and suggest to replace with the breakpoint mixin
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚢
Changes proposed in this Pull Request
stylelint
errors manuallystylelint --fix
selector-max-id
rule in few files where IDs were used extensively (mostly stuff like Calypso's#secondary
/#footer
or TinyMCE IDs)Testing instructions
npm run lint:css
and confirm no more errorsRelated
/client/**
#32350reformat-files:css
script #32351