Skip to content

docs(wp-interactivity-api): Add WordPress 6.9 client navigation requirements#15

Open
derintolu wants to merge 1 commit intoWordPress:trunkfrom
derintolu:fix/wp-interactivity-router-6.9-requirements
Open

docs(wp-interactivity-api): Add WordPress 6.9 client navigation requirements#15
derintolu wants to merge 1 commit intoWordPress:trunkfrom
derintolu:fix/wp-interactivity-router-6.9-requirements

Conversation

@derintolu
Copy link

Summary

Adds documentation for the WordPress 6.9 requirement that script modules must be explicitly marked as compatible with client-side navigation.

Per Interactivity API's client navigation improvements in WordPress 6.9:

For other script modules registered "manually", developers must use the add_client_navigation_support_to_script_module method of the main WP_Interactivity_API instance.

Without this, the router will not intercept link clicks on pages using manually registered script modules.

Changes

  • SKILL.md: Updated client-side navigation section with WP 6.9+ requirements
  • references/router.md: Added new reference document with full router documentation

Key Addition

// Mark module as compatible with client-side navigation (WordPress 6.9+ REQUIRED)
wp_interactivity()->add_client_navigation_support_to_script_module('my-navigation');

For blocks, use block.json:

{
  "supports": {
    "interactivity": { "clientNavigation": true }
  }
}

Test Plan

  • Verified this requirement on a production WordPress 6.9 site
  • Confirmed router does not intercept links without this call
  • Confirmed router works correctly after adding this call

🤖 Generated with Claude Code

…rements

Per https://make.wordpress.org/core/2025/11/12/interactivity-apis-client-navigation-improvements-in-wordpress-6-9/

Script modules must be explicitly marked as compatible with client-side
navigation using wp_interactivity()->add_client_navigation_support_to_script_module()

Changes:
- Add WordPress 6.9+ requirements section to SKILL.md
- Update client-side navigation setup steps
- Add router.md reference with full documentation
- Add debugging step to check for data-wp-router-options attribute

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@github-actions
Copy link

github-actions bot commented Feb 6, 2026

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.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: derintolu <derintolu@git.wordpress.org>

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

@fellyph fellyph requested a review from Jameswlepage February 11, 2026 08:51
@derintolu derintolu marked this pull request as draft February 17, 2026 01:46
@derintolu derintolu marked this pull request as ready for review February 17, 2026 01:48
- if it uses custom bundling, confirm module output is supported.

### 6) Debug common failure modes
### 6) Client-side navigation with the Router

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TBF this could be asked about all of the existing committed skills, but what's the point of dumping all this information here if it's available via references?


- If repo build constraints are unclear, ask: "Is this using `@wordpress/scripts` or a custom bundler (webpack/vite)?"
- Consult:
- `references/router.md` - **READ THIS FIRST for navigation issues**

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should avoid yelling out our models since this needs to service more than just Anthropic

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

Comments