Allow direct linking to site health check result

[sippis]

It would be neat if directly linking to a site health check result would be possible. The link should open the linked check to show the description.

Use case: plugin is checking if site can communicate with a necessary 3rd party server. Communication with that server is mission critical for the plugin functionality to work. There's check for that in site health, and in case of failure also admin notice. Health check description contains more explanation of possible causes and instructions how to fix. In this case, it would make a lot of sense to have direct link in the notice to the test having that description.

[audrasjb]

Hello, I support this proposal at 100%!
I'm moving this to milestone 6.8 since I think I should be able to work on this one, but other PRs are welcome!

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

This PR does the following changes:

• Add an ID to each accordion button
• On page load, get the hash and open the related accordion
• Update the URL hash each time an accordion button is clicked

This way, people can use the URL of the page to share a direct link to the site health info section they want.
Note: As a first iteration, this changeset doesn't add any UI button.

[audrasjb]

@sippis the above PR is a first iteration on this feature. It doesn't add any button but you can just use the URL of the screen after clicking any Site Health Info section. Does it work on your side?

[audrasjb]

Testing instruction partially provided in the PR.

Please note that this pull request can't be tested on the Playground link provided in the PR as Playground cannot interact with URL hashes.

[pratiklondhe]

Test Report

Description

This report validates whether the indicated patch works as expected.

Patch tested: ​https://patch-diff.githubusercontent.com/raw/WordPress/wordpress-develop/pull/8184.diff

Environment

• WordPress: 6.8-alpha-20250222.101448
• PHP: 8.1.29
• Server: nginx/1.26.1
• Database: mysqli (Server: 8.0.35 / Client: mysqlnd 8.1.29)
• Browser: Firefox 135.0
• OS: macOS
• Theme: Twenty Twenty-Five 1.1
• MU Plugins: None activated
• Plugins:
  • Test Reports 1.2.0

Actual Results

1. ❌ While the accordion with the hash id got highlighted, the accordion did not expand as expected ( attaching a video of the test )

Additional Notes

• It seems the code added in the on-load is not getting executed at all

[vgnavada]

Test Report

Description

This report validates whether the indicated patch works as expected.

Patch tested: ​https://github.com/WordPress/wordpress-develop/pull/8184

Environment

• WordPress: 6.8-alpha-20250123.235129
• PHP: 7.4.31-dev
• Server: PHP.wasm
• Database: WP_SQLite_Translator (Server: 5.5 / Client: 3.40.1)
• Browser: Chrome 133.0.0.0
• OS: macOS
• Theme: Twenty Twenty-Five 1.0
• MU Plugins: None activated
• Plugins:
  • Test Reports 1.2.0

Actual Results

✅ Each Site Health section has a unique ID, making it possible to reference them via URL fragments.

<button id="health-check-section-wp-paths-sizes".......>
<button id="health-check-section-wp-active-theme"......>
<button id="health-check-section-wp-plugins-inactive"..>

✅ The accordion panels are correctly referenced using aria-controls, ensuring proper structure.

<button id="health-check-section-wp-core" aria-controls="health-check-accordion-block-wp-core">

✅ Clicking a section manually expands it as expected.

❌ However, when accessing a section using a direct URL with a hash fragment (e.g., #health-check-section-wp-core), the section does not expand automatically.

❌ The page loads, but it doesn’t scroll to or expand the relevant section.

❌ Additionally, window.location.hash does not return the expected value in the console, which might indicate a script interfering with the URL fragment handling.

Additional Notes

• The setup for direct linking is in place, but the expected behavior isn’t working yet.

Supplemental Artifacts

Add Inline:

[audrasjb]

As per today's bug scrub: It appears this ticket still needs some work. As 6.8 beta 1 is very close, I'm moving it to 6.9. Feel free to move it back to 6.8 if it can be committed by Monday.

[SirLouen]

There are two existing patch reports for the given patch.
Removing needs-testing, as @audrasjb suggests, more work is required into this patch

@sippis can you provide more information to help develop a better patch according to what audrasjb initially submitted?