Add hash handling to site health accordions - Refreshing 8184.diff

[nikunj8866]

Trac ticket: https://core.trac.wordpress.org/ticket/62846

---

This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

Core Committers: Use this line as a base for the props when committing in SVN:

Props nikunj8866, westonruter.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[github-actions]

Test using WordPress Playground

The changes in this pull request can previewed and tested using a WordPress Playground instance.

WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser.

Some things to be aware of

• The Plugin and Theme Directories cannot be accessed within Playground.
• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[westonruter]

Will this be sufficient for async tests which run after the page has loaded?

[nikunj8866]

@westonruter No, wp.domReady() only waits for the DOM to be ready (like DOMContentLoaded), not for async content or tests that run after the page has loaded.

[westonruter]

So then isn't this running too early? It should run after all of the async tests have completed.

[nikunj8866]

The Site Tools > Info tab data is loaded statically, so there aren't any async tests involved. In this case, wp.domReady() is fine to use. Existing test reports also show no issues, so it seems to be working as expected.

Are you seeing any problem with it?