Chrome Redesign: Routing Issues
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 970
- Forks
- 486
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 170
Description
Problem Statement
Navigation using the back button in the browser or in the app should work as expected. There are some issues we have identified were state management is not behaving correctly, any other issues around state management should be grouped under this issue.
BACK AND FWD IN BROWSER SHOULD WORK AS EXPECTED (NOT THE DOJO PORTLETS UNLESS THEY ALREADY WORK THEN THEY SHOULDN'T STOP WORKING)
Steps to Reproduce
Acceptance Criteria
Navigation and back stack work as expected.
dotCMS Version
Current.
Proposed Objective
User Experience
Proposed Priority
Priority 3 - Average
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
https://dotcms.freshdesk.com/a/tickets/33810
Assumptions & Initiation Needs
No response
Quality Assurance Notes & Workarounds
No response
Sub-Tasks & Estimates
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reproducing browser back and forward navigation in the current version, then trace the routing and state-management flow. Done means the navigation and back stack work as expected without regressing Dojo portlets.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100