SSWConsulting / SSWConsulting/SSW.Website
🐛 Bug - UX - Dropdown Menu Keeps Open on Link Click - Should be Closed so Users Can See the Content
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
Requested by: Marina Gerber via YakShaver.ai 🦬
cc: Marina Gerber, @brookjeynes-ssw, @adamcogan, @babakamyljanovssw
Hi Team!
Url from screen share: https://www.ssw.com.au/consulting
Pain
Fix the issue where the dropdown box does not minimise when clicking the 'SSW Services' button on the SSW Website (Dev - Next.js). The dropdown should minimise upon clicking the button to allow users to navigate further into the services offered.
Acceptance Criteria
- The dropdown box minimises when the 'SSW Services' button is clicked.
- Users can navigate further into the services offered without needing to click below the button.
- The functionality is consistent across all browsers supported by the SSW Website.
Reproduce Steps
- Navigate to the SSW Website (Dev - Next.js).
- Locate the 'SSW Services' button.
- Click the 'SSW Services' button.
- Observe that the dropdown box does not minimise.
- Click below the button to see the dropdown minimise.
Screenshot

Figure: Dropdown box fails to minimize after button click
Contributor guide
No contributing guide indexed for this repository
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
Start by reproducing the issue on the SSW Website development page at https://www.ssw.com.au/consulting and trace the SSW Services dropdown implementation in the Next.js project. Verify the click behavior across supported browsers, and consider the work done when clicking the button closes the dropdown and allows users to navigate the services without clicking elsewhere.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- next.js
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100