Forms: fix block styles not loading in CIAB environment.

[simison]

Fixes FORMS-533

Proposed changes:

• Change how we load styles to be closer to the regular way.

Before

After

Other information:

• Have you written new tests for your changes, if applicable?
• Have you checked the E2E test CI results, and verified that your changes do not break them?
• Have you tested your changes on WordPress.com, if applicable (if so, you'll see a generated comment below with a script to run)?

Jetpack product discussion

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

Testing instructions:

• Test blocks in regular admin page/post editor, site editor, and CIAB page editor.
• Confirm that block loads styles. You'd see placeholder break, labels miss bold text, or fields like slider look broken.

[github-actions]

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 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:

The Jetpack plugin has different release cadences depending on the platform:

• WordPress.com Simple releases happen as soon as you deploy your changes after merging this PR (PCYsg-Jjm-p2).
• WoA releases happen weekly.
• Releases to self-hosted sites happen monthly:
  • Scheduled release: February 3, 2026
  • Code freeze: February 3, 2026

If you have any questions about the release process, please ask in the #jetpack-releases channel on Slack.

[github-actions]

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 fix/forms-styles-ciab branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack fix/forms-styles-ciab

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

[Copilot]

Pull request overview

This pull request aims to fix an issue where form block styles were not loading in the CIAB (Create in App Builder) environment by consolidating the asset loading approach.

Changes:

• Consolidated script and style loading into a single method using Assets::register_script() with css_path parameter
• Removed the separate load_editor_styles() method and its associated enqueue_block_assets hook
• Moved the enqueue_block_editor_assets hook registration from the plugin file into the register_block() method

Reviewed changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 1 comment.

File	Description
projects/plugins/jetpack/extensions/blocks/contact-form/contact-form.php	Removed asset loading hooks, keeping only block registration
projects/plugins/jetpack/changelog/fix-forms-styles-ciab	Added changelog entry for the fix
projects/packages/forms/src/blocks/contact-form/class-contact-form-block.php	Consolidated asset loading logic and moved hook registration into register_block()
projects/packages/forms/changelog/fix-forms-styles-ciab	Added changelog entry for the fix

[Copilot]

This line should be removed. The wp_enqueue_style() call is attempting to enqueue a style that hasn't been registered yet. The Assets::register_script() call below (with 'enqueue' => true and 'css_path' => '../../../dist/blocks/editor.css') will automatically register and enqueue both the script and its associated stylesheet, making this manual enqueue call unnecessary and incorrect.

Suggested change

wp_enqueue_style( 'jp-forms-blocks' );

[jp-launch-control]

Code Coverage Summary

Coverage changed in 2 files.

File	Coverage	Δ%	Δ Uncovered
projects/plugins/jetpack/extensions/blocks/contact-form/contact-form.php	0/3 (0.00%)	0.00%	-3 💚
projects/packages/forms/src/blocks/contact-form/class-contact-form-block.php	551/609 (90.48%)	1.32%	-9 💚

Full summary · PHP report · JS report

[enejb]

Since this is a public function I think we should add a deprecation notice before removing it.
Since it could cause fatal errors or any plugin that also calls it.