-
Notifications
You must be signed in to change notification settings - Fork 812
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
Contact form block - add example #13629
Conversation
Caution: This PR has changes that must be merged to WordPress.com |
Thank you for the great PR description! When this PR is ready for review, please apply the Scheduled Jetpack release: November 5, 2019. |
MichaelArestad, Your synced wpcom patch D33495-code has been updated. |
MichaelArestad, Your synced wpcom patch D33495-code has been updated. |
This seems to now work (even though I can't get it to work). I'll take another shot at it in the morning and stub out all the fields to match the mockup. |
MichaelArestad, Your synced wpcom patch D33495-code has been updated. |
MichaelArestad, Your synced wpcom patch D33495-code has been updated. |
MichaelArestad, Your synced wpcom patch D33495-code has been updated. |
There appears to be a display bug for blocks with innerblocks. There's a negative left/right margin set that makes the preview look not so great. |
MichaelArestad, Your synced wpcom patch D33495-code has been updated. |
Added style overrides to core styles. Creating an issue in Gberg shortly and will link to it, but this will work in the meantime. |
Gutenberg issue: |
Looks great and works as expected! |
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.
The @wordpress/block-editor
package used in this PR was only added to WordPress in version 5.2:
https://core.trac.wordpress.org/ticket/46429
Since Jetpack is currently compatible with WordPress 5.1, we can't use this just yet.
However, and as per the discussion in #13620, we should be able to update that requirement to WP 5.2 in the release after the next, once WordPress 5.3 is released for everyone.
Should we wait to merge this until Jetpack 8.0 and our new compatibility change?
Another alternative would be to up our version requirement to WP 5.2 in this release already, but I am afraid this could be problematic for all the folks that still run WordPress 5.1.
@jeherve Ah! I had no idea. I was just trying to fix some warnings. I'll revert those changes. |
MichaelArestad, Your synced wpcom patch D33495-code has been updated. |
@jeherve fixed |
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 looks good to me. Merging!
Master issue: #13510
Changes proposed in this Pull Request:
Before
After
Before/After of the field text alignment and bg color fixes:

Is this a new feature or does it add/remove features to an existing part of Jetpack?
Testing instructions:
Proposed changelog entry for your changes: