-
Notifications
You must be signed in to change notification settings - Fork 800
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
Remove recurring-payments button color #24801
Conversation
The Payments Button button color was hardcoded to white (#fff). The button itself's color could be overriden by using the editor controls but the outline style just meant the button was invisible - white on white backgrounds. This has been fixed by removing the rule completely - I can't see why it exists. Another approach would have been to use the currentColor pseudo-color. Fixes #24768
Caution: This PR has changes that must be merged to WordPress.com |
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 🤖 The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available. Once your PR is ready for review, check one last time that all required checks (other than "Required review") appearing at the bottom of this PR are passing or skipped. Jetpack plugin:
|
@aaronrobertshaw added you as a reviewer on the off-chance you can remember if there was a set of specific circumstances leading to this change two years ago. It might just be that lots of other stuff has changed since :) |
Thanks for the ping @dsas. From my vague memory, this was related to maintaining the existing styling of the button when it was switched to an inner block in #15915. I also have a recollection that at the time there were some catches around maintaining the old SubmitButton's fallback colors and AMP styling for what is now the legacy AMP theme. As you note, I can't see why it's still required unless it is only for old deprecated recurring-payment button's markup. It's been a long time since I've waded into Jetpack waters but this PR is testing as advertised for me. I'd prefer to leave final approval to the Jetpack crew in case my lack of familiarity with Jetpack these days has caused me to overlook something. |
Tests well. |
Great news! One last step: head over to your WordPress.com diff, D82951-code, and deploy it. Thank you! |
Deployed r247796-wpcom |
Fixes #24768
Changes proposed in this Pull Request:
The Payments Button button color was hardcoded to white (#fff). The
button itself's color could be overriden by using the editor controls
but the outline style just meant the button was invisible - white on
white backgrounds.
This has been fixed by removing the rule completely - I can't see why
it exists. Another approach would have been to use the currentColor
pseudo-color.
Jetpack product discussion
Does this pull request change what data or activity we track or use?
No
Testing instructions: