Skip to content
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

🐛 Bug: Standardize the container style on the mobile device #1482

Closed
jagpreetrahi opened this issue Mar 9, 2025 · 6 comments
Closed

🐛 Bug: Standardize the container style on the mobile device #1482

jagpreetrahi opened this issue Mar 9, 2025 · 6 comments
Labels
🐛 Bug Indicates that the issue is a bug or defect. Status: Triage This is the initial status for an issue that requires triage.

Comments

@jagpreetrahi
Copy link
Contributor

Describe the bug

When accessing the Use Cases page on a mobile device without enabling the desktop site view, users may encounter inconsistent container styles and difficulty viewing the content within these containers. This issue stems from the current implementation of the page's layout, which may not be fully optimized for mobile responsiveness.

Steps To Reproduce

Go to Use Case on mobile device.
Check there the content inside container not able to see properly due to container size overlap

Expected Behavior

Responsive Containers: Containers should adjust their dimensions based on the screen size, ensuring content is neither truncated nor misaligned.

Readable Content: Text and images within containers should scale appropriately, maintaining readability and visual appeal without requiring users to zoom or scroll excessively.

Screenshots

With desktop Site on mobile

Image

Without desktop site on mobile

Image

Device Information [optional]

- OS:
- Browser:
- version:

Are you working on this issue?

Yes

Do you think this work might require an [Architectural Decision Record (ADR)]? (significant or noteworthy)

Yes

@jagpreetrahi jagpreetrahi added Status: Triage This is the initial status for an issue that requires triage. 🐛 Bug Indicates that the issue is a bug or defect. labels Mar 9, 2025
@jagpreetrahi
Copy link
Contributor Author

Hey @benjagm , I hope you are doing well , could you please assign me this issue, so that I can make a PR request for that

@idanidan29
Copy link
Contributor

Hey @jagpreetrahi, there's already an issue and a PR for this. You can check it out here.

@jagpreetrahi
Copy link
Contributor Author

Hey @idanidan29, yeah, I noticed that issue too when I did a cross-check. Since we’re facing a similar problem, how about we collaborate to resolve it together?

Looking forward to your response

@idanidan29
Copy link
Contributor

@jagpreetrahi There is already a PR solving this problem. I'd be happy to collaborate with you on further issues if needed.

@jagpreetrahi
Copy link
Contributor Author

Alright

@DhairyaMajmudar
Copy link
Member

Closing as duplicate of #1445

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug Indicates that the issue is a bug or defect. Status: Triage This is the initial status for an issue that requires triage.
Projects
None yet
Development

No branches or pull requests

3 participants