-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Indicate how to get to Specs Page from Runner (minor style tweaks to sidebar) #21873
Comments
➤ Mark Noonan commented: Chris Baus Jennifer Shehane I see this one as pretty high priority, especially with the specs list defaulting to closed. |
The code for this is done in cypress-io/cypress#22069, but has yet to be released. |
Released in This comment thread has been locked. If you are still experiencing this issue after upgrading to |
Summary
The navigation item in the left hand menu that goes to Specs is styled in an “inert” state, as the active item in the menu.
During the bug hunt, several Cypress employees on a video call with me could not see how to get back to the specs list from the runner, which is fair since the link that navigates there is not styled to be clickable (other links have
cursor: pointer
and hover states, this does not, since we are already inside that part of the app). This video shows the problem in more detail:https://www.loom.com/share/f95449b235474cf2b2d0ef096122c764
The fix here is small: since every item in the side bar is a valid navigation target from the Spec Runner, they should all look and behave the same way so the user knows it is valid to click any of the three items, so we should turn off the “active” state of the spec item.
This was part of the feedback noted in https://cypress-io.atlassian.net/browse/UNIFY-1667 - but the title of that ticket would make it harder to track.
Acceptance Criteria
Resources
Any Notion documents, Google documents, Figma Boards
┆Issue is synchronized with this Jira Task by Unito
┆author: Mark Noonan
┆epic: UI/UX Improvements
┆friendlyId: UNIFY-1688
┆priority: Medium
┆sprint: Fast Follows 1
┆taskType: Task
The text was updated successfully, but these errors were encountered: