SSWConsulting / SSWConsulting/SSW.Website
🐛 Bug - Sidebar Width Issue on Safari
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
Requested by: @griffenedge via YakShaver.ai 🦬
cc: @griffenedge, @designbyalex, @brookjeynes-ssw, @adamcogan, @babakamyljanovssw
Hi Team!
🟥 Watch the video (1 min 30 sec)
Url from screen share: https://www.ssw.com.au/ssw/Company/Offices/Sydney
Pain
The sidebar on the SSW Sydney office page is constrained to an inappropriate width on Safari, affecting content display. This issue does not occur on other browsers like Chrome.
Acceptance Criteria
- The sidebar on the SSW Sydney office page should display correctly on Safari, matching the width and layout seen on Chrome.
- Ensure the sidebar content is fully visible and not constrained.
- Verify that the left column content adheres to WCAG guidelines, with a maximum of 80 characters per line.
Reproduce Steps
- Open Safari browser.
- Navigate to the SSW Sydney office page on the SSW Website (Dev - Next.js).
- Observe the sidebar width and compare it to the same page on Chrome.
- Check the left column content for line length compliance with WCAG guidelines.
Screenshot

Figure: Safari sidebar width issue on SSW Sydney office page
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 with the SSW Sydney office page at the URL in the issue, comparing its Safari and Chrome rendering in the Dev - Next.js site. Locate the page implementation and styling responsible for the sidebar and left column; done means Safari matches Chrome, the sidebar content is fully visible, and left-column lines meet the stated WCAG constraint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nextjs
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100