ApplicationState - Remove center alignment rule

[zamoore]

📌 Summary

If merged, this PR removed a style rule that center-aligns the ApplicationState component.

🛠️ Detailed description

The current implementation of the ApplicationState component has a margin: 0 auto; rule on the root element (.hds-application-state). This forces a center alignment of the component, which consumers need to override.

In order to make adoption of this change as smooth as possible, we have added a new @isAutoCentered attribute to the root level ApplicationState component. This argument defaults to true and applies the margin: 0 auto; style rule via the hds-application-state--is-auto-centered class. This behavior can be disabled by setting @isAutoCentered to false.

🔗 External links

Jira ticket: HDS-3584

---

👀 Component checklist

• Percy was checked for any visual regression
• A changelog entry was added via Changesets if needed (see templates here)

💬 Please consider using conventional comments when reviewing this PR.

📋 PCI review checklist

• If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
• If applicable, I've worked with GRC to document the impact of any changes to security controls.
  Examples of changes to controls include access controls, encryption, logging, etc.
• If applicable, I've worked with GRC to ensure compliance due to a significant change to the in-scope PCI environment.
  Examples include changes to operating systems, ports, protocols, services, cryptography-related components, PII processing code, etc.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Updated (UTC)
hds-showcase	Ready	Preview	Oct 6, 2025 2:24pm
hds-website	Ready	Preview	Oct 6, 2025 2:24pm

[didoo]

Now that we have removed the self-alignment, probably we should update the showcase to have two variants (default + center-aligned) for some of the cases (eg. when it's in a container) because I think in most of the cases, the empty state will be visually centered (in a page, or in a table, or in a card). As far as I remember, the request came from Atlas/TFC and was an exception.

Which leads me to this consideration: what if introducing this change as is now (which is definitely breaking, will impact a lot of places, and can't be codemoded but will require a lot of manual checks) we define a new argument - @hasMarginAuto or @autoCenter or or something similar - that by default is true (so non-breaking) but that consumers can turn off if/when needed?

[zamoore]

Now that we have removed the self-alignment, probably we should update the showcase to have two variants (default + center-aligned) for some of the cases (eg. when it's in a container) because I think in most of the cases, the empty state will be visually centered (in a page, or in a table, or in a card). As far as I remember, the request came from Atlas/TFC and was an exception.

Which leads me to this consideration: what if introducing this change as is now (which is definitely breaking, will impact a lot of places, and can't be codemoded but will require a lot of manual checks) we define a new argument - @hasMarginAuto or @autoCenter or or something similar - that by default is true (so non-breaking) but that consumers can turn off if/when needed?

I really like the idea of introducing a new property. autoCenter sounds good to me. This is similar to what we did for isInline in the icon component, so it has precedent.