Skip to content

Forms: Migrate form fields to inner blocks JETPACK-262 - #42890

Merged
talldan merged 102 commits into
trunkfrom
update/migrate-form-fields-to-inner-blocks
Jun 4, 2025
Merged

talldan merged 102 commits into
trunkfrom
update/migrate-form-fields-to-inner-blocks

Conversation

@aaronrobertshaw

@aaronrobertshaw aaronrobertshaw commented Apr 3, 2025 •

Copy link
Copy Markdown
Contributor

JETPACK-262

Fixes #42358

⚠️ This PR is now the sole source of truth for both adding new base form field blocks and migrating fields to them ⚠️

Proposed changes:

  • Add new base blocks for form fields:
    • Input
    • Label
    • Option
    • Options
  • Migrate all form fields to use new base blocks
    • File field is pending and will be updated to inner blocks in due course
  • Fixes for various minor forms bugs on trunk e.g. undo loops, minor style conflicts etc
  • Change consent and checkbox fields to share option styles not label/input styles for better consistency across fields

Does this pull request change what data or activity we track or use?

No changes.

Testing instructions:

General Notes

  • Please test undo and redo actions throughout all sequences. A number of improvements in this PR specifically enhance stability during these interactions
  • As this PR is still under active development and testing, these test instructions may need to evolve over time.

  1. 🧱 Field Insertion & Pasting

Goal: Confirm all form field blocks insert and behave as expected.

  • Insert each of the following field types via the block inserter:
    • Text, Name, Email, Number, Website, Phone, Multiline (Textarea)
    • Dropdown
    • Checkbox, Terms Consent
    • Single Choice (Radio), Multiple Choice (Checkbox),
    • Date Picker
  • Paste a field from one form into another.
  • Confirm all fields look correct, show relevant block controls, and function as expected.

⸻

  1. 🎨 Styling: Inputs, Labels, and Options

Goal: Confirm block and global styles apply and override correctly.

  • Apply styles via Global Styles (site editor).
  • Apply per-block styles using the block inspector.
  • Confirm styles render consistently in both the editor and frontend.
  • Test toggling individual styles on/off and reapplying.

⸻

  1. 🔁 Style Syncing Between Fields

Goal: Verify how styles are shared across synced fields of similar types.

  • Update a style on one synced field (e.g., font size or text color for an input field).
  • Confirm other synced input fields update accordingly.
  • Opt a field out of syncing and confirm it no longer updates.
  • Insert a new field and confirm it inherits current synced styles.
  • Paste a field from another form into a synced form and observe behavior.

⸻

  1. 🔀 Field Transforms

Goal: Ensure transforming between field types behaves as expected.

  • Transform fields (e.g., Name → Email, Text → Phone).
  • Confirm that styles and attributes are preserved only when appropriate.
  • Confirm that irrelevant attributes (like a "Name" label value when transforming to an Email field) are discarded.

⸻

  1. 🧩 Form Variations & Patterns

Goal: Ensure all form patterns insert correctly and render well.

Test inserting:

  • Contact Form
  • RSVP Form
  • Registration Form
  • Appointment Form
  • Feedback Form
  • Lead Capture Form
  • Salesforce Lead Form

Verify:

  • The default structure is valid and editable.
  • Labels, placeholders, and field types are appropriate.

⸻

  1. ✨ Style Variants

Goal: Validate style variations and layout combinations.

Insert:

  • Outlined Style Form
  • Animated Style Form

For both, test:

  • Base version
  • Version with field customizations
  • Upgrading from trunk form to refactor form
  • Confirm styles work.
  • Test columns and responsive behavior.

⸻

  1. 📦 Field Nesting

Goal: Confirm fields can be used within layout blocks.

  • Nest fields inside:
    • Group blocks
    • Columns
  • Confirm style syncing still works across nesting levels.
  • Check alignment and spacing behave as expected.

⸻

  1. 🪄 Automatic Form Wrapping

Goal: Ensure orphaned fields are auto-wrapped in a Form block.

  • Insert a field outside any form block.
  • Paste one or more fields into a blank page.
  • Confirm automatic wrapping behavior.
  • Save and verify layout remains valid.

⸻

  1. ⚙️ Required Field Settings

Goal: Validate required state control across all field types.

  • Toggle required setting for fields via field and inner blocks' block toolbars
  • Confirm required indicator displays appropriately.
  • Add custom required text and check that it renders.
  • Disable the required setting and confirm the indicator disappears.

⸻

  1. 🧪 Deprecations & Migrations

Goal: Confirm legacy forms upgrade smoothly.

  • On trunk, create a post containing all field types and apply styling.
  • Switch to the PR branch.

Confirm:

  • Legacy form still displays correctly on the frontend
  • No block validation errors in editor
  • Fields are migrated to inner block structure
  • Styling remains intact
  • Save the post and confirm the frontend still matches.

⸻

  1. 🌐 Additional Coverage

🧑‍🦯 Keyboard Accessibility

  • Tab through all form fields and verify correct focus behavior.
  • Ensure field labels are associated correctly (label-input relationships).

📱 Mobile Responsiveness

  • Test forms on small screens (phone/tablet viewports).
  • Confirm layouts stack properly and remain usable.

↔️ RTL Language Support

Switch the site language to RTL (e.g., Hebrew, Arabic).

Check that:

  • Layouts flip direction as expected
  • Labels and fields align correctly

♻️ Reusable Blocks

  • Save a form or field group as a reusable block.
  • Insert it into another post.
  • Confirm editing and layout integrity.

⚙️ Editor Performance

  • Insert lots of fields (30+).
  • Check for lag or editor slowdown during typing and style changes.

🌍 Multilingual / i18n Support

  • Switch site language.
  • Confirm labels, placeholders, and help texts are translatable and update correctly.

@aaronrobertshaw aaronrobertshaw added Enhancement Changes to an existing feature — removing, adding, or changing parts of it [Feature] Forms [Status] In Progress [Block] Form Form block (also see Form package label) Triaged [Package] Forms [Feature] Forms Blocks Blocks designed to streamline user input and engagement, such as contact, newsletter sign-ups, etc. labels Apr 3, 2025
@aaronrobertshaw aaronrobertshaw self-assigned this Apr 3, 2025
@github-actions

github-actions Bot commented Apr 3, 2025 •

Copy link
Copy Markdown
Contributor

Thank you for your PR!

When contributing to Jetpack, we have a few suggestions that can help us test and review your patch:

  • ✅ Include a description of your PR changes.
  • ✅ Add a "[Status]" label (In Progress, Needs Review, ...).
  • ✅ Add a "[Type]" label (Bug, Enhancement, Janitorial, Task).
  • ✅ Add testing instructions.
  • ✅ Specify whether this PR includes any changes to data or privacy.
  • ✅ Add changelog entries to affected projects

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:

  1. Ensure all required checks appearing at the bottom of this PR are passing.
  2. Make sure to test your changes on all platforms that it applies to. You're responsible for the quality of the code you ship.
  3. You can use GitHub's Reviewers functionality to request a review.
  4. When it's reviewed and merged, you will be pinged in Slack to deploy the changes to WordPress.com simple once the build is done.

If you have questions about anything, reach out in #jetpack-developers for guidance!


Jetpack 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.

@github-actions

github-actions Bot commented Apr 3, 2025 •

Copy link
Copy Markdown
Contributor

Are you an Automattician? Please test your changes on all WordPress.com environments to help mitigate accidental explosions.

  • To test on WoA, go to the Plugins menu on a WoA dev site. Click on the "Upload" button and follow the upgrade flow to be able to upload, install, and activate the Jetpack Beta plugin. Once the plugin is active, go to Jetpack > Jetpack Beta, select your plugin (Jetpack), and enable the update/migrate-form-fields-to-inner-blocks branch.
  • To test on Simple, run the following command on your sandbox:
bin/jetpack-downloader test jetpack update/migrate-form-fields-to-inner-blocks

Interested in more tips and information?

  • In your local development environment, use the jetpack rsync command to sync your changes to a WoA dev blog.
  • Read more about our development workflow here: PCYsg-eg0-p2
  • Figure out when your changes will be shipped to customers here: PCYsg-eg5-p2

@jp-launch-control

jp-launch-control Bot commented Apr 3, 2025 •

Copy link
Copy Markdown

Code Coverage Summary

Coverage changed in 8 files. Only the first 5 are listed here.

File Coverage Δ% Δ Uncovered
projects/packages/forms/src/contact-form/class-contact-form-field.php 516/862 (59.86%) 4.46% 61 💔
projects/packages/forms/src/contact-form/class-contact-form.php 560/917 (61.07%) -4.08% 59 💔
projects/packages/forms/src/contact-form/class-contact-form-plugin.php 411/1014 (40.53%) 7.50% 15 💔
projects/packages/forms/src/blocks/contact-form/variation-picker.js 0/24 (0.00%) 0.00% 2 ❤️‍🩹
projects/packages/forms/src/blocks/contact-form/util/form.js 0/20 (0.00%) 0.00% 1 ❤️‍🩹

88 files are newly checked for coverage. Only the first 5 are listed here.

File Coverage
projects/packages/forms/src/blocks/deprecated/field-option-checkbox/index.js 0/4 (0.00%) 💔
projects/packages/forms/src/blocks/deprecated/field-option-radio/index.js 0/4 (0.00%) 💔
projects/packages/forms/src/blocks/field-checkbox/deprecated.js 0/3 (0.00%) 💔
projects/packages/forms/src/blocks/field-checkbox/edit.js 0/16 (0.00%) 💔
projects/packages/forms/src/blocks/field-checkbox/index.js 0/2 (0.00%) 💔

Full summary · PHP report · JS report

Coverage check overridden by Coverage tests to be added later Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR .

@aaronrobertshaw
aaronrobertshaw force-pushed the add/new-form-field-blocks branch from 1ce694a to 9bcd54d Compare April 6, 2025 23:36
@aaronrobertshaw
aaronrobertshaw force-pushed the update/migrate-form-fields-to-inner-blocks branch from a2fb901 to 4688f4e Compare April 6, 2025 23:36
@andrewserong

Copy link
Copy Markdown
Member

Just jotting down a note from testing: overall it's been working quite well for me so far! There's one issue with the Dropdown Field block that I ran into that looked a bit peculiar so just noting it down for now:

  1. In the Site Editor, go to edit a page and add a Registration Form pattern (it includes a Dropdown Field)
  2. In the Page tab on the right hand sidebar, click the button next to Template and then Swap Template
  3. This opens the modal to select another template. In the preview of the current template, the Dropdown Field appears to go into an infinite loop setting itself up (this doesn't appear to happen on trunk):
2025-04-07.15.58.31.mp4
Screenshot of verbose logging from React in the console

I'm not quite sure what's going on, but there's lots of verbose logging messages from React:

image

Unrelated to this PR, but I find the ability to edit options within the Dropdown Field pretty challenging. That appears to be the case in both this PR and on trunk, though, but could be good to circle back to further down the track.

@aaronrobertshaw
aaronrobertshaw force-pushed the update/migrate-form-fields-to-inner-blocks branch from e57e555 to c6627ea Compare April 7, 2025 07:25
@aaronrobertshaw

Copy link
Copy Markdown
Contributor Author

the Dropdown Field appears to go into an infinite loop setting itself up (this doesn't appear to happen on trunk):

Thanks for the testing @andrewserong 🚀

All patterns at this stage will have legacy blocks that need to run through the block deprecations. I'd recently seen a similar issue to what you described when only some blocks had been migrated previously. It's on my list to dig deeper into but got sidetracked today fixing the style syncing for option blocks across the different field types.

@aaronrobertshaw

aaronrobertshaw commented Apr 7, 2025 •

Copy link
Copy Markdown
Contributor Author

In the Site Editor, go to edit a page and add a Registration Form pattern (it includes a Dropdown Field)

I hit a block validation error as soon as I attempted to add a Registration Form or the pattern. After tweaking the dropdown field's edit component to be a little more robust, I could replicate the issue you noted.

My suspicion is that this could be related to the useSyncStyleAttributes hook. Adding an early return to that prevented the bouncing but the dropdown field never got setup to be the custom select.

Quick update: For now I've added a super basic check for whether we're in the template preview mode. In that scenario, the style syncing will return early. This seems to stabilize the preview however the custom JS select field doesn't seem to get setup. That's something I'll look into after some higher priority issues.

@aaronrobertshaw
aaronrobertshaw force-pushed the update/migrate-form-fields-to-inner-blocks branch from 1a776ae to 86c2780 Compare April 7, 2025 09:01
@aaronrobertshaw
aaronrobertshaw force-pushed the add/new-form-field-blocks branch from 2171100 to dd0c310 Compare April 7, 2025 23:29
@aaronrobertshaw
aaronrobertshaw force-pushed the update/migrate-form-fields-to-inner-blocks branch from 86c2780 to 608e4d8 Compare April 7, 2025 23:29
@andrewserong

Copy link
Copy Markdown
Member

Another couple of wrinkles that might have already been captured elsewhere (Label block issues):

Hitting "Enter" from the beginning of a label block adds a new line character, where I'd expect it to insert a paragraph block preceding the parent block:

2025-04-08.13.07.00.mp4

When removing the text from a Label field altogether, if you click out from the block and attempt to click back into it, it's not possible to start typing to add in label text again. You can get back to it via the up arrow by keyboard, but I imagine it's that we're not able to click the empty rich text field. Maybe we can add placeholder text while the Label block is selected or something like that?

2025-04-08.13.07.26.mp4

@aaronrobertshaw

Copy link
Copy Markdown
Contributor Author

Appreciate the continued testing @andrewserong 🙇

Hitting "Enter" from the beginning of a label block adds a new line character, where I'd expect it to insert a paragraph block preceding the parent block

This is the same behaviour as trunk at the moment but definitely something that can be improved.

When removing the text from a Label field altogether, if you click out from the block and attempt to click back into it, it's not possible to start typing to add in label text again

Nice catch, that should be an easy enough fix. Until recently the label block had an auto width, I probably just missed also making the RichText component fill the available width when I tweaked the block for that same purpose.

I'll get an issue up for the first enhancement and tweak the other one shortly on this branch to hopefully avoid it tripping up others testing.

@talldan talldan left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've run out of time, so this is a partial review.

Comment on lines +36 to +35
'jetpack/field-required': 'required',
'jetpack/field-defaultValue': 'defaultValue',

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor - I feel like 'jetpack/field/defaultValue' might be preferable to reduce the mix of camel/kebab case mixing. I find it reads a little easier too.

Comment on lines +34 to +54
if ( innerBlocks.length !== 2 ) {
return true;
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this condition is a good idea, because if another inner block type (e.g. a validation message block) is added in the future to the multiple choice block, isEligible would return true incorrectly, and that'll cause the migration to run when it shouldn't.

This kind of logic problem with isEligible has caused some bad bugs in the gutenberg codebase:

Maybe removing this if condition and reducing it to the innerBlocks.some check below is enough.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Either way this isEligible check would need to be updated upon the addition of any validation inner block. For the time being, it's slightly quicker to check the length first.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, though there are ways that will make it more future proof:

  • Return true if the are only option blocks, false otherwise
  • Return false if there's a label and/or an options block present, true otherwise.

Both ways it wouldn't matter if a future new block type is supported.

select => select( blockEditorStore ).getBlock( clientId ).innerBlocks,
[ clientId ]
);
const options = innerBlocks?.[ 1 ]?.innerBlocks;

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This could be made more robust, just in case the blocks are reordered for some reason,


const noop = () => undefined;

export default function DropdownFieldEdit( props ) {

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpick

Suggested change
export default function DropdownFieldEdit( props ) {
export default function SelectFieldEdit( props ) {

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd like to settle on what the field should be called and use that consistently. The original form components named the block field-select however gave the block a human readable label of "Dropdown" which was also used in the code too e.g. JetpackDropdown.

Should this be "dropdown" as that's what most users might expect or "select" given it represents an actual select input?

Comment on lines +34 to +54
if ( innerBlocks.length !== 2 ) {
return true;
}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as for the other block, maybe this can be removed and it'll make the isEligible check more future-proof.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As noted here, it won't make the check more future proof as the check below would still have to be updated in the event of further valid inner blocks being added

if ( ! empty( $attributes['options'] ) && is_string( $attributes['options'] ) ) {
$attributes['options'] = array_map( 'trim', explode( ',', $attributes['options'] ) );

// TODO: Work out where these values are set? Are they actually set anywhere?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could it be set by using a shortcode like [contact-field type="checkbox-multiple" values="1,2,3" /]?

Perhaps that was an old version of the shortcode.

I see there's also some code here to construct a shortcode with a values attribute like that:

if ( ( $att === 'options' || $att === 'values' ) && is_string( $val ) ) { // remove any empty strings
$val = explode( ',', $val );
}
if ( is_array( $val ) ) {
$val = array_filter( $val, array( __CLASS__, 'remove_empty' ) ); // removes any empty strings
$att_strs[] = esc_html( $att ) . '="' . implode( ',', array_map( array( __CLASS__, 'esc_shortcode_val' ), $val ) ) . '"';

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, I came to the same conclusion it was for BC purposes. Thanks for looking into it.

@aaronrobertshaw

Copy link
Copy Markdown
Contributor Author

🐛 Known Issue 🐛

Unfortunately, I think I broke the style syncing when adding some fields to a form. Possibly in: 9954d62.

It will be worked on over the next couple of days, so ignore bugs there for the moment.

ramonjd and others added 27 commits June 4, 2025 13:59
…yle is active (on frontend) (#43534)

* Fix rogue typography attributes from input applying to label

* Fix bad rebase

* Update tests
* Forms: Enhance class handling in contact form plugin and tests

- Updated class handling in `class-contact-form-plugin.php` to filter empty block style classes.
- Modified test cases in `Contact_Form_Plugin_Test.php` and `Contact_Form_Test.php` to include additional attributes and ensure proper class wrapping for various field types.
- Improved assertions to validate class attributes in rendered output.

* Make innerblocks optional. Just for linting
* Fix text input-style field label font size when outlined style is active.

* Remove scaling using variable

* Fix scaling of multiple option fields when using outlined style

* Tidy up styles

* Wrap labels

* Fix outlined label font size and animation

* Fix animation by ensuring top is a valid value

* Remove will-change: transform on frontend too. Transform usually does not change.
…3545)

* Ensure that existing font-weight styles do not override block and global label styles.

* Consent weights

* Revert options positioning kram

* Increase specificity to 0 1 0 for classic themes

* Bump specificity of consent label

* Bump specificity
* Fix animated style label font size in editor

* Add span wrapper around label text

* Update animated label styles on frontend

* Size and animation adjustments for required text

* Fix label animating when selected in editor if using the animated form style variation and no placeholder is set
* Fix animated label vertical centering when using uneven borders in the input

* Remove unused cass var
* Remove text color support for jetpack/options, since frontend does not replicate the markup of the editor and so style parity cannot be achieved

* Try to fix tests

* Whoops, wrong flag

* One more time

---------

Co-authored-by: Andrew Serong <14988353+andrewserong@users.noreply.github.com>
* Refactor contact form styles and rendering logic to enhance alignment and maintainability. Update CSS for radio and checkbox options to use consistent alignment, and streamline fieldset and div class attributes by removing unnecessary prefixes. Improve handling of border styles and attributes for outlined forms, ensuring compatibility with global styles.

* Try baseline for the options

* Revert changes to "fix" option alignment

* Revert option alignment v2

* Add classes to tests

* Reinstate tweaks for option positioning

* Apply wp-block-jetpack-option class in the attribute migration method

* Use em instead of rem. Remove unnecessary tweaks

* Border support for classic themes

* Ensure radio inputs don't warp in classic themes. Update options description

* Force opinionated dimensions on the options inputs

* wp-block-jetpack-option was not being applied to inner options blocks
…with trunk (#43634)

* consolidate legends

* Remove styles that are inconsistent with existing trunk spacing. (frontend)

* Remove padding in editor

* editor

* The feature branch has different markup for .wp-block-jetpack-options so we need to target the fieldset using different selectors

* comments
…s function (#43653)

* Attempt to fix warnings about PhanUndeclaredTypeParameter for WP_Block

* Forms: Update border radius and width handling in deprecateFieldStyles function

* Ensure border radius and width are correctly set to 'undefined' only when they are not provided or are null, allowing for proper handling of zero values.

* Coerce lineheight to str

* REvert  - bad rebase

* Update class-contact-form-plugin.php

My IDE auto formatted this

---------

Co-authored-by: Andrew Serong <14988353+andrewserong@users.noreply.github.com>
* Outlined multi option backgrounds defaults

* Don't concat the label and option styles for consent and single option in unmigrated forms

* PHPCS warning - Use statements are not alphabetically sorted (MediaWiki.Classes.UnsortedUseStatements.UnsortedUse
* initial commit - adding extra markup to the select rendering and fixing positioning of labels

* uncommenting

* Remove default select border

* Update select field rendering to include a wrapper div with the correct class structure for improved styling and consistency in tests.

* Update contact form styles to inherit text color and adjust z-index for select wrapper elements

* Only run `getAttribute` on select wrapper if there is one

* Reinstate padding change

* phan me

* phanos

* whitespace
… to select dropdown and fix z-index (#43721)

* Enhance select field transformation by adding default placeholder for input block. Update contact form plugin to correctly reference placeholder attribute. Adjust z-index values in CSS for improved label positioning.

* Update z-index values in contact form CSS for improved label positioning and remove redundant styles for outlined fields.

* Complete CSS comment

* Refactor select field transformation to set placeholder attribute directly from attributes. Remove redundant placeholder handling in inner block creation.

* Revert createTextFieldInnerBlocks

* Revert experiment. Add default placeholder for select in createTextFieldInnerBlocks

* Don't mutate the attributes object

* Don't spread optional chaining just in case
…s. Add 'color: unset !important;' to both editor.scss and grunion.css for consistent input appearance. (#43737)
…43759)

* Forms: Refactor placeholder handling in contact form fields

* Simplify placeholder logic to ensure consistent rendering of input fields.
* Remove unnecessary conditionals for placeholder assignment and improve code clarity.

* Forms: Update contact form styles and placeholder handling

* Adjusted placeholder logic to ensure it only renders when a value is present, improving input field consistency.
* Updated the contact form stylesheet to include a version query string for better cache management.
* Commented out specific CSS rules to prevent unintended side effects related to placeholder visibility in outlined and animated label styles.

* Remove other :not(:placeholder-shown) styles
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

[Block] Form Form block (also see Form package label) Coverage tests to be added later Use to ignore the Code coverage requirement check when tests will be added in a follow-up PR E2E Tests Enhancement Changes to an existing feature — removing, adding, or changing parts of it [Feature] Forms Blocks Blocks designed to streamline user input and engagement, such as contact, newsletter sign-ups, etc. [Feature] Forms [Package] Forms [Plugin] Jetpack Issues about the Jetpack plugin. https://wordpress.org/plugins/jetpack/ [Tests] Includes Tests Triaged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Forms: Migrate form fields to inner blocks

7 participants