Forms: Fix outline style label font size

[talldan]

Fixes and issue I noticed while working on JETPACK-277

Note - this merges into #42890 rather than trunk.

Proposed changes:

If a user creates a form and uses the Outlined form style variation, they can no longer adjust the global styles font size of labels for any inputs that are focused, have a placeholder, or if the field is a Single/Multi choice field. This only happens in #42890, in trunk it works fine.

The issue is that we're attempting to use a font-size: 0.8em to scale the font to a smaller size when a field is focused, but this rule completely overrides the font-size applied by global styles. Block styles can also override the 0.8em, so have the opposite effect.

The fix I've taken is to move the font-size: 0.8em rule to a child element, so it correctly scales the inherited font size from any global/block styles that are set on the parent. In the editor there's already a child element that can serve this purpose. On the frontend, there is no element, so a new span has been added. This might be a good idea anyway, as it makes the markup more like the editor, although it's not an exact match.

As part of this, the PR also updates the scaling of the required text, which is usually 85% of the size of the label so that it works consistently.

With the font size moved to a different element, a new transition also has to be implemented for the font-size scaling, otherwise it looks jarring when clicking into or out of a field.

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

p1747968046579529-slack-C02A76B714Z

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

No

Testing instructions:

1. Add a contact form
2. With the form selected, change to the 'Outlined' style variation in the block inspector
3. Select one of the inputs and type some placeholder text in
4. Go to Global Styles > Blocks > Label and change the font size to something noticabely different (e.g. XL or XXL)

Expected: The font size should visible change:

Before: The font size stayed the same:

[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/outline-style-label-font-size branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack fix/outline-style-label-font-size

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

[talldan]

For most fields, transform actually doesn't change it stays at transform: translateY(-50%);, so I've removed this.

[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 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 🤖

---

🔴 Action required: Please add missing changelog entries for the following projects: projects/packages/forms

Use the Jetpack CLI tool to generate changelog entries by running the following command: jetpack changelog add.
Guidelines: /docs/writing-a-good-changelog-entry.md

---

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!

[jp-launch-control]

Code Coverage Summary

No summary data is available for parent commit 85bb6ed, so cannot calculate coverage changes. 😴

If that commit is a feature branch rather than a trunk commit, this is expected. Otherwise, this should be updated once coverage for 85bb6ed is available.

Full summary · PHP report · JS report