MEMBERS-DIRECTORY-001L — Restore People-finder submit focus after search completion - #642
Merged
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This was referenced Aug 14, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #641
Officer impact: No live officer workflow changes. In preserved connected source, keyboard focus returns to the exact People-finder name input or Search button displaced by one current search, but only when native disablement left no meaningful focus; focus deliberately moved elsewhere is preserved.
Officer documentation: SYSTEM_DESIGN.md, IMPLEMENTATION_PLAN.md, SECURITY.md, and docs/officers/EVENTS_SHOP_MEMBERS.md.
Deployment evidence: Source and tests only. No website or Firebase deployment, provider configuration, account/sign-in action, or production-data action. Availability remains hard false and production remains the inert #623 preview.
Scope
The intent contains no query, name, result, photo, account ID, request ID, or service value. It creates no request, retry, result, Clear action, audit, service call, or data URL. App/admin changes, editing, Clear, unmount, and stale completions are fenced. #507 retains every backend/privacy/authorization/staging/availability/publication/live gate. Active #616 paths and its separate SECURITY hunk are unchanged.
Verification
Exact head: 5166c92
Tree: 0a2deecc78c1c1645c50db8a1b79f991df41f580
Parent/base: 3ca02e1
Exact binary diff SHA-256: a1a8630995701e001af2c5fdfd256c01d9c022f457329fceef17f17d34024696