Update the shopping cart skeleton.

[StevenDufresne]

Fix: #98526

This PR attempts to align the shopping cart skeleton more closely with the final state to reduce visual shift on load. There isn't a perfect state for the skeleton since the number and type of products change the cart's layout.

I've focused on making the top section of the left side align on load. Specifically the title, the site name, the first product title, and the price. Having those align, in my opinion, significantly reduces shift.

Screenshots

Before

Screen.Capture.on.2025-01-24.at.10-16-22.mp4

After

Screen.Capture.on.2025-01-24.at.09-46-11.mp4

Screen.Capture.on.2025-01-24.at.09-43-25.mp4

Stills

Before	After	Final

RTL

Before	After	Final

Why are these changes being made?

It's not that the current skeleton is bad, it isn't, but I believe that reducing any extra cognitive load in shopping carts is a worthwhile pursuit. They communicate a lot about a product.

Pinging design for feedback:
@Automattic/dotcom-design

Testing Instructions

• Add different types of items to your cart
• Navigate to your cart
• Verify the skeleton matches the cart later.

Test RTL

Repeat the same test with your account set to a RTL language like Arabic.

Pre-merge Checklist

• Has the general commit checklist been followed? (PCYsg-hS-p2)
• Have you written new tests for your changes?
• Have you tested the feature in Simple (P9HQHe-k8-p2), Atomic (P9HQHe-jW-p2), and self-hosted Jetpack sites (PCYsg-g6b-p2)?
• Have you checked for TypeScript, React or other console errors?
• Have you used memoizing on expensive computations? More info in Memoizing with create-selector and Using memoizing selectors and Our Approach to Data
• Have we added the "[Status] String Freeze" label as soon as any new strings were ready for translation (p4TIVU-5Jq-p2)?
  • For UI changes, have we tested the change in various languages (for example, ES, PT, FR, or DE)? The length of text and words vary significantly between languages.
• For changes affecting Jetpack: Have we added the "[Status] Needs Privacy Updates" label if this pull request changes what data or activity we track or use (p4TIVU-aUh-p2)?

[github-actions]

Calypso Live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-130912

Jetpack Cloud live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-130912&env=jetpack

Automattic for Agencies live (direct link)

https://calypso.live?image=registry.a8c.com/calypso/app:build-130912&env=a8c-for-agencies

[matticbot]

Here is how your PR affects size of JS and CSS bundles shipped to the user's browser:

Sections (~139 bytes added 📈 [gzipped])

name                          parsed_size           gzip_size
checkout                           +430 B  (+0.0%)     +139 B  (+0.0%)
site-purchases                     +175 B  (+0.0%)      +57 B  (+0.0%)
purchases                          +175 B  (+0.0%)      +57 B  (+0.0%)
jetpack-cloud-partner-portal       +175 B  (+0.0%)      +57 B  (+0.0%)
a8c-for-agencies-purchases         +175 B  (+0.0%)      +57 B  (+0.0%)
a8c-for-agencies-client            +175 B  (+0.0%)      +57 B  (+0.0%)

Sections contain code specific for a given set of routes. Is downloaded and parsed only when a particular route is navigated to.

Async-loaded Components (~139 bytes added 📈 [gzipped])

name                                             parsed_size           gzip_size
async-load-calypso-my-sites-checkout-modal            +430 B  (+0.0%)     +139 B  (+0.0%)
async-load-calypso-blocks-editor-checkout-modal       +430 B  (+0.0%)     +139 B  (+0.0%)

React components that are loaded lazily, when a certain part of UI is displayed for the first time.

Legend

What is parsed and gzip size?

Parsed Size: Uncompressed size of the JS and CSS files. This much code needs to be parsed and stored in memory.
Gzip Size: Compressed size of the JS and CSS files. This much data needs to be downloaded over network.

Generated by performance advisor bot at iscalypsofastyet.com.

[crisbusquets]

cc @fcoveram, as he was adjusting the checkout design 👀

[jasmussen]

Outstanding. This feels a substantial improvement as far as preventing layout shifts. Works well:

I also tested zooming in on the page while the skeleton was blinking, just to see if anything would be off as part of that, but that doesn't seem the case.

Looking at the code, it also looks overall improved. And finally, this doesn't appear to affect negatively any future efforts in this same space.

---

Happy to give it a ✅, though I saw some other issues as I was testing this. I'm 95% sure it's unrelated, but just to be sure, let me know and I can re-test and open separate issues if need be. First is this:

The cart dropdown opens far removed from the button.

Secondly, I saw an overflow issue as things were loading:

To be fair, that's all sections, and only when loading fresh from cache, and mostly in small browser windows. It may be my curious browser choice (Vivaldi, Chromium based), or it may hint at an overflow issue.

Can you repo any of those?

[sirbrillig]

The cart dropdown opens far removed from the button.

Ugh. Thanks for noticing! I've created a bug report for this here. I'll try to track down what changed.

• Masterbar shopping cart dropdown no longer appears near cart button #98893

[sirbrillig]

This looks good to me! Thank you for updating this. I'm not sure if it's changed much since the original checkout rebuild in 2020.