Componentry: remove Jetpack color overrides on core components#47317
Componentry: remove Jetpack color overrides on core components#47317
Conversation
|
Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.
Interested in more tips and information?
|
|
Thank you for your PR! When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:
This comment will be updated as you work on your PR and make changes. If you think that some of those checks are not needed for your PR, please explain why you think so. Thanks for cooperation 🤖 Follow this PR Review Process:
If you have questions about anything, reach out in #jetpack-developers for guidance! Boost plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. Protect plugin: No scheduled milestone found for this plugin. If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack. |
There was a problem hiding this comment.
Pull request overview
This pull request removes Jetpack color overrides on core WordPress components across multiple plugins and packages, allowing components to use default WordPress core styling. This is part of a larger effort (spin-off from PR #47056) to reduce custom styling and improve consistency with WordPress core.
Changes:
- Removed
--wp-admin-theme-color*CSS custom property overrides from multiple plugin and package stylesheets - Removed custom toggle styling to rely on WordPress core toggle components
- Removed custom button styling including border-radius overrides and secondary button styles
- Removed unused
--jp-highlightCSS variable from root variables
Reviewed changes
Copilot reviewed 19 out of 19 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| projects/plugins/protect/src/js/styles.module.scss | Removed color theme overrides and focus border width customization |
| projects/plugins/boost/app/assets/src/css/main/wp-admin.scss | Removed color theme overrides and secondary button styling (has issue with remaining variable reference) |
| projects/plugins/boost/app/assets/src/css/admin-banner.scss | Removed custom CTA button styling (background, border, color, hover, focus states) |
| projects/packages/videopress/src/client/admin/components/video-thumbnail/style.module.scss | Removed spinner color override |
| projects/packages/search/src/dashboard/components/module-control/style.scss | Removed custom toggle styling and related variables |
| projects/packages/publicize/_inc/components/admin-page/toggles/styles.module.scss | Removed toggle color override |
| projects/packages/publicize/_inc/components/admin-page/toggles/social-notes-toggle/styles.module.scss | Removed toggle color override |
| projects/packages/my-jetpack/_inc/style.module.scss | Removed color theme overrides |
| projects/js-packages/components/components/toggle-control/styles.module.scss | Removed toggle color override |
| projects/js-packages/components/components/button/style.module.scss | Removed color theme overrides and border-radius customization |
| projects/js-packages/base-styles/root-variables.scss | Removed unused --jp-highlight variable |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| @@ -11,11 +11,6 @@ p { | |||
| } | |||
| // Override WordPress component styles | |||
| .jb-dashboard { | |||
There was a problem hiding this comment.
The custom override for --wp-admin-theme-link-color has been removed, but this variable is still referenced on lines 36 and 40 of this file. Since the custom override was #{variables.$gray_90}, removing it means these elements will now use WordPress core's default link color instead of the previous gray color. This could result in a visual change. If this is intentional, the references should ideally be updated to either use the core variable directly or be removed if the default behavior is desired.
There was a problem hiding this comment.
They might still be needed, but needs a closer look:
jetpack/projects/plugins/boost/app/assets/src/css/main/wp-admin.scss
Lines 40 to 46 in 83e5487
These also are related and need a closer look to see what they actually affect:
jetpack/projects/plugins/boost/app/assets/src/css/main/wp-admin.scss
Lines 96 to 105 in 83e5487
Code Coverage SummaryThis PR did not change code coverage! That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷 |
| color: variables.$primary-black; | ||
| background: none; | ||
| border: 1px solid variables.$primary-black; | ||
| padding: 8px 24px; | ||
| border-radius: 3px; | ||
| font-weight: 600; | ||
| cursor: pointer; | ||
| font-size: 16px; | ||
| line-height: 24px; |
There was a problem hiding this comment.
Some non-color changes here so need to double check where it was applied in Boost and check properly.
Spin-off from #47056
Jetpack components mostly rely on core components under the hood, with added features and style overrides on spacing/colors.
This PR focuses on removing color overrides everywhere where we used core components under the hood. I'll do functional changes and straight component-replacements in separate PR so that this can be tested easier.
Proposed changes:
--wp-admin-theme-color*style overrides on componentry.--jp-highlightCSS variable.Other information:
Jetpack product discussion
Does this pull request change what data or activity we track or use?
Testing instructions:
Changelog