Support the new Review Notes Experiment on a block-by-block basis#267
Support the new Review Notes Experiment on a block-by-block basis#267jeffpaul merged 10 commits intoWordPress:developfrom
Conversation
…eview on a block by block basis
…ere added. Add basic styles to button to avoid the load state overlapping the border
|
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 If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message. To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
|
Could also bury this option a bit more by placing it within the vertical 3 dot menu where the "Add note" button/link is. No real strong opinion on this, happy to land this as-is and iterate from community feedback. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #267 +/- ##
==========================================
Coverage 57.48% 57.48%
Complexity 563 563
==========================================
Files 35 35
Lines 2907 2907
==========================================
Hits 1671 1671
Misses 1236 1236
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…is with a loading spinner instead
Yeah, wasn't sure exactly where to put this. It's nice at the top-level because it's easy to find but I never loved it there (easy to be confused on what it actually is). I've moved it to the nested menu now |
As far as I can find (and had Claude and Cursor look as well) there's only two available slots here for us to use. One is what we're using now which drops things into the section before the section that has the Delete button (with no controls on where it shows in that section). Or there's a unstable API that adds it as the very first item in that menu. That may be better positioning though has the risk of using the unstable API.
I can update that to match
I'm assuming you'd not just want to update the icon to be the shortcut but then also have that keyboard shortcut trigger this functionality? If so, the problem here is the loading state only shows on the button. So if someone uses the keyboard shortcut when the block is selected but they don't have that menu open, there isn't a loading state that shows (so no real way for them to know something is happening). I can look into ways to add a loading animation to the entire block if we think the keyboard shortcut would be useful. Worth noting two other things:
|
|
Bah, I'd say just merge as-is and we can iterate once 7.0 is out and we get some feedback on the feature. No need to chase down these last couple of bits. |

What?
In #260 we added an Experiment to review all your blocks and add Notes with review suggestions. This PR brings that same functionality to the individual block level, allowing you to run a review on an individual block instead of across all blocks.
Why?
All the core functionality is in place to support review on a single block and there may be times where a user wants to review a single block (think a single paragraph) rather than having to review the entire post. So this PR adds the ability to trigger review on a single block.
How?
BlockSettingsMenuControlsto add a block toolbar button to supported blocks that can be used to trigger review. This is nested under the block More menuUse of AI Tools
Used both Claude Code and Cursor running Sonnet 4.6 and GPT-5.3 Codex respectively to plan changes and implement most of those changes, with final review, testing and cleanup done by me
Testing Instructions
npm i && npm run build && composer installScreenshots or screencast