Social: Update share status modal to use Dataviews component

[manzoorwanijk]

Share status modal on mobile looks messed up. See #39051 (comment)

Proposed changes:

• Make use of DataViews component to render the list of shares
• Thus, fix the mobile view

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:

• Enable the share status feature - define( 'JETPACK_SOCIAL_HAS_SHARE_STATUS', true );
• Goto the post editor for a post which has some shares or reshare posts to create a few entries (at least 10)
• Click on "View share history" in the publicize panel
• Confirm that the modal and data renders correctly
• Confirm that the modal content is scrollable when the data is more than what can be displayed in the modal at once
• Confirm that the mobile view isn't squeezed and is rather horizontally scrollable

BEFORE	AFTER
Destop view
Mobile view

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

---

The e2e test report can be found here. Please note that it can take a few minutes after the e2e tests checks are complete for the report to be available.

---

Follow this PR Review Process:

1. Ensure all required checks appearing at the bottom of this PR are passing.
2. Choose a review path based on your changes:
   • A. Team Review: add the "[Status] Needs Team Review" label
     • For most changes, including minor cross-team impacts.
     • Example: Updating a team-specific component or a small change to a shared library.
   • B. Crew Review: add the "[Status] Needs Review" label
     • For significant changes to core functionality.
     • Example: Major updates to a shared library or complex features.
   • C. Both: Start with Team, then request Crew
     • For complex changes or when you need extra confidence.
     • Example: Refactor affecting multiple systems.
3. Get at least one approval before merging.

Still unsure? Reach out in #jetpack-developers for guidance!

[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 WordPress.com Simple 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, and enable the update/social-share-status-modal-to-use-dataviews branch.

  • For jetpack-mu-wpcom changes, also add define( 'JETPACK_MU_WPCOM_LOAD_VIA_BETA_PLUGIN', true ); to your wp-config.php file.

• To test on Simple, run the following command on your sandbox:

  bin/jetpack-downloader test jetpack update/social-share-status-modal-to-use-dataviews
  

  bin/jetpack-downloader test jetpack-mu-wpcom-plugin update/social-share-status-modal-to-use-dataviews
  

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

[gmjuhasz]

I think it would be better to call this Shared at or something similar

[manzoorwanijk]

Then the continuation of the sentence doesn't read nice "Shared at 2 minutes ago", where as, "Time" can be read as its own clause.

[gmjuhasz]

To me, time feels too vague, also I looked up on the designs it's 'Published at' on the admin page, maybe that's where I got the idea from :D I think Shared at still makes more sense than published at. Either way we should use the same term here and there in the future, even if that's time

[manzoorwanijk]

But what about the case of failure? We can't say "Shared at".

[gmjuhasz]

That's a point we have to make on the admin page designs too, but let's leave time now then

[manzoorwanijk]

Build failure being discussed at p1725456184868289-slack-C05Q5HSS013

[gmjuhasz]

This looks a lot better thanks for the refactor!

Just a minor comment, the View ExternalLink changed to black from the previous color, can we retain that?

[manzoorwanijk]

Just a minor comment, the View ExternalLink changed to black from the previous color, can we retain that?

Fixed. Thanks