Landing page responsiveness issues on Galaxy S24 Ultra in Chrome
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Active
- Tech stack
- react, typescript
Research direction
Start by opening the Kromacut landing page in Chrome at the Galaxy S24 Ultra mobile viewport and compare its sections, navigation, controls, and text with the desktop layout. Identify the affected sections and reproduce the reported visual problems; done means the mobile layout is readable and usable, the reported viewport is verified or matched by an equivalent, and desktop remains correct.
Written by the indexing model from the issue text.
Description
The landing page does not display correctly on a phone and needs a responsiveness review.
Reported test environment:
- Device: Samsung Galaxy S24 Ultra
- Browser: Google Chrome
To reproduce, open the Kromacut landing page in Chrome on the device and browse the page at its mobile viewport size.
Expected: the landing page adapts to the phone screen with readable content, correctly sized and positioned elements, and usable navigation and controls.
Actual: the user reports that the landing page does not look right in terms of responsiveness. Specific affected sections and screenshots have not yet been provided.
Review and fix the mobile layout, verify the result on the reported device/browser or an equivalent viewport, and check that desktop layout remains correct.
- Dominant language
- TypeScript
- Stars
- 290
- Forks
- 32
- Avg merge
- 6h 2m
- Merged PRs (30d)
- 7
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from vycdev/Kromacut
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
-
Experimental WebAssembly acceleration for compute-heavy algorithmsMay be free again @vycdev claimed this 79 days ago, and no pull request is open. Openenhancement
-
enhancement good first issue help wanted
Difficulty 5/5 Over a week Newbie friendliness 55/100
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 42/100
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
microsoft/playwright#43327 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/TypeScript#64758 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
opensearch-project/OpenSearch-Dashboards#12937 ·
Maintainers usually reply within 2 days
-
Liveness marks block-included attesters live in the block's epoch instead of the attestation's epochOpen
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
status: needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
a2ui-project/a2ui#3158 ·
Maintainers usually reply within 2 days