MHR | Return to the registration table with the same filters
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
### Summary
The feature allows registry analysts to return to the registration table exactly as they left it—preserving filters, sort order, scroll position, and highlighted row—after reviewing a registration. This improves workflow efficiency by eliminating the need to reapply settings when navigating between multiple records.
### UI Suggestions
**Close Button Placement**
- Place a clearly labeled “Close” or “Back to Table” button at the top-right and/or bottom of the registration detail view.
- Use a consistent icon (e.g., ← or ✖) with a tooltip: “Return to previous table view”.
**Sticky Table State**
Use session storage to retain:
- Active filters
- Sort order
- Scroll position
- Highlighted row
Optionally display a message like: “Returning to your previous view…” for clarity.
**Visual Feedback**
- Briefly highlight the previously selected row upon return to reinforce continuity.
**Fallback View**
- If no session data is found, display a banner: “Default view loaded – previous session expired or unavailable.”
**Accessibility**
- Ensure keyboard navigation and screen reader support for the Close button and restored table view.
Please refer to parent ticket for details (Acceptance Criteria. Business Rules etc)
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the parent ticket for the missing acceptance criteria and business rules, then trace the registration table and registration detail view. Verify how navigation currently handles filters, sorting, scroll position, and the highlighted row before defining the session state and return path. Done means returning to the table restores the specified state, includes the fallback and accessibility behavior, and preserves a clear path when no session data exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100