Forms: Update unread indicator

[enejb]

This PR updates the unread indicator to be more like it was designed.

Before:

After:

Proposed changes:

• Update the design of the Unread indicator to be more like designed/

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

See p1HpG7-xmp-p2

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

no

Testing instructions:

Visit the dashboard. Mark something as unread.
Notice the new design.

[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 update/forms-move-unread-indicator branch.
• To test on Simple, run the following command on your sandbox:

bin/jetpack-downloader test jetpack update/forms-move-unread-indicator

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

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

---

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!

[Copilot]

Pull Request Overview

This PR updates the unread indicator design in the Forms dashboard to better align with the intended design. The indicator changes from a text-based bullet point to a solid circular badge positioned over the avatar.

• Redesigned unread indicator as a circular badge with background color and border
• Applied unread styling (bold text) to the IP Address field for consistency

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
projects/packages/forms/src/dashboard/inbox/style.scss	Updated CSS for unread indicator to render as a solid circular badge with absolute positioning over the avatar
projects/packages/forms/src/dashboard/inbox/dataviews/index.js	Applied wrapperUnread to IP Address field to make it bold when unread, consistent with other fields
projects/packages/forms/changelog/update-forms-move-unread-indicator	Added changelog entry documenting the design update

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The CSS properties font-size and color are no longer needed since the indicator now uses background-color with overflow: hidden to create a solid colored dot. The text content (●) inside the span is hidden and these font-related properties serve no purpose. Consider removing these redundant properties to improve code clarity.

Suggested change

	color: #d63638;
	background-color: #d63638;
	overflow: hidden;
	font-size: 8px;
	background-color: #d63638;
	overflow: hidden;

[jp-launch-control]

Code Coverage Summary

This PR did not change code coverage!

That could be good or bad, depending on the situation. Everything covered before, and still is? Great! Nothing was covered before? Not so great. 🤷

Full summary · PHP report · JS report

[simison]

A bit unclear what should happen when we then allow hiding the avatar (#45692)

Not a blocker necessarily now, but would make next steps harder. It's a bit under convo still (p1761944997981159-slack-C05QAFZSFTL)

We're also discussing (internal ref pgzWbf-3n3-p2) about how to implement & how unread notifications should look like, so perhaps it's better to change all at once once we're more settled on both approaches? Mainly so that we don't change it to users back-and-forth too many times in.

[ilonagl]

It would be better to wait a bit on this one, until we align internally. 🙏