SSWConsulting / SSWConsulting/SSW.Website

🐛 Bug - App download links not in the viewport on mobile screen sizes

Open
#3,986 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Needs Refinement YakShaver
Dominant language
HTML
Stars
14
Forks
10
Avg merge
13h 51m
Merged PRs (30d)
38

Description

Requested by: @0xharkirat via YakShaver.ai 🦬
cc: @0xharkirat, @brookjeynes-ssw, @adamcogan, @babakamyljanovssw

Hi Team!

  🟥  Watch the video (1 min 6 sec)

  Url from screen share: https://ssw.com.au/products/rewards

Pain

Users are experiencing difficulty accessing important links on the QR code redirect page because they are not immediately visible in the viewport. This requires users to scroll down, creating an unnecessary roadblock.

Acceptance Criteria
  1. When a user scans the QR code, the redirected page should display the important links within the initial viewport.
  2. The layout should be adjusted so that users do not need to scroll to access the download links.
  3. Ensure compatibility across different mobile devices and screen sizes.
Reproduce Steps
  1. Scan the QR code that redirects to ssw.com.au/products/rewards.
  2. Observe that the important links are not immediately visible in the viewport.
  3. Scroll down to find the links, noting the inconvenience caused.
Screenshot

Screenshot
Figure: Links not in viewport after QR code scan

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at https://ssw.com.au/products/rewards and reproduce the QR-code redirect issue on mobile-sized viewports. Inspect the page layout and determine why the download links fall below the initial viewport; done means the important links are visible without scrolling across the mobile screen sizes described in the acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Tech stack
html, nextjs
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.