WordPress 7.1 can attach an inline Note to a selected piece of text instead of an entire block. Editorial work then changes that text through typing, paste, transform, move, autosave, revision restore, and simultaneous edits. The test must distinguish a Note that follows its intended text from one that silently points at the wrong sentence.
Use this before teams depend on inline Notes for legal review, client approval, accessibility feedback, translation, regulated copy, or high-volume editorial collaboration.
Quick answer
WordPress 7.1 Inline Notes Text Selection Revision Drift Test should be handled with a narrow evidence-first workflow: build ambiguous text cases, change each boundary, transform and move blocks, then verify the result before making broader changes.
What to check first
- Create a controlled paragraph with repeated phrases, links, bold text, inline code, punctuation, and a second identical sentence.
- Attach Notes to the start, middle, and end of selections, then insert and delete text before, inside, and after each anchor.
- Copy, paste, split, merge, transform, duplicate, and move the block while recording which Note follows which text.
- Create autosaves and revisions, restore an older revision, and confirm the Note state matches the restored content policy.
- Run a two-editor conflict test with synthetic content and capture save order, revision IDs, Note anchors, and visible results.
Diagnostic table
Use this table to keep the work practical. It connects the symptom to evidence and a verification step.
| Action | Evidence to collect | How to verify |
|---|
| Build ambiguous text cases | Create a controlled paragraph with repeated phrases, links, bold text, inline code, punctuation, and a second identical sentence. | Each Note remains on the intended text or displays an explicit unresolved state. |
| Change each boundary | Attach Notes to the start, middle, and end of selections, then insert and delete text before, inside, and after each anchor. | Repeated phrases never cause a silent move to the wrong occurrence. |
| Transform and move blocks | Copy, paste, split, merge, transform, duplicate, and move the block while recording which Note follows which text. | Revision restore produces a documented and understandable Note result. |
| Restore revisions | Create autosaves and revisions, restore an older revision, and confirm the Note state matches the restored content policy. | Two-editor saves do not lose feedback without visible conflict or audit evidence. |
Why this usually happens
- Text anchors need more than a raw character offset when earlier content changes.
- Repeated phrases make text-only matching ambiguous.
- Block transforms can replace client IDs or markup while preserving visible words.
- Revision restore and collaborative save order can change content and Note state on different timelines.
Useful command or data shape
Adapt paths, IDs, and privacy handling to the site before running commands or storing data on production.
anchor_case:
block_client_id: synthetic-paragraph-01
selected_text: review this claim
repeated_phrase_count: 2
operation: insert_before_selection
expected_anchor: original_first_occurrence
actual_anchor: record_after_save
Safe fix order
Do the work in a sequence that makes each result easy to prove. Stop if a step produces new evidence that changes the incident scope.
- Build ambiguous text cases
- Change each boundary
- Transform and move blocks
- Restore revisions
- Test two editors
Decision rule
Approve inline Notes for a workflow only when a Note either stays attached to the intended text or becomes visibly unresolved. A silent jump to another matching phrase is more dangerous than a clear detached state.
What to tell the client or owner
Share the block type, selected text, repeated phrase count, operation, save order, revision IDs, expected anchor, actual anchor, and whether the Note became unresolved.
Production verification checklist
- Each Note remains on the intended text or displays an explicit unresolved state.
- Repeated phrases never cause a silent move to the wrong occurrence.
- Revision restore produces a documented and understandable Note result.
- Two-editor saves do not lose feedback without visible conflict or audit evidence.
Mistakes to avoid
- Do not test only unique one-sentence paragraphs.
- Do not skip copy-paste and block transforms.
- Do not assume a visible Note after restore is attached to the correct revision text.
- Do not use client approval Notes until detached and deleted-state behavior is documented.
Questions teams ask during testing
What should happen when selected text is deleted?
The safest behavior is a clearly unresolved Note with enough context for a reviewer to decide whether to reattach or close it. Silent deletion can erase review evidence.
Should Notes be part of content revisions?
That is a product and governance decision. Test the actual Beta behavior, then document whether content restore also restores, removes, or leaves collaboration state unchanged.
When HandL WP should help
HandL WP should help when editorial Notes carry approval or compliance significance. We can reproduce anchor drift, preserve revision evidence, and define a workflow that does not mistake visible feedback for correct feedback.
If this is active on a production site, test WordPress 7.1 editorial collaboration.
Related HandL WP guides
Use these related guides when the same issue touches tracking, security, checkout, or crawler visibility.
Helpful references